go-ultimate

Solid

The complete Go development skill. REQUIRED for ALL Go work — writing, refactoring, reviewing, generating, scaffolding, or discussing Go code, including any change to .go files. Use whenever the user mentions Go, Golang, go.mod, a Go package, or asks to build a Go backend service, CLI, library, script, MCP server (Model Context Protocol), or AI/LLM agent with tool calling or ReAct-style reasoning. Routes by project type to the right architecture, conventions, and review checklist. Highly opinionated; overrides generic Go style and lint guidance on conflicts.

AI & Automation 22 stars 2 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
45
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Go Ultimate Skill A single, opinionated skill for writing the best Go programs — synthesized from four general-Go skills, four agent/MCP donors (one donor, eino, contributes two documents), the Google and Uber style guides, and a repository/production-practice donor. Opinions represent the synthesized consensus; where the donors disagreed, this skill resolved the conflict per the precedence ladder below. ## When this skill applies **Always**, for any Go work: code generation, refactoring, code review, architecture and style discussions, scaffolding, or any change to `.go` files. It overrides generic Go style/lint guidance when they conflict. ## Setup — resolving `<skill-dir>` Several instructions in this skill reference `<skill-dir>` — the absolute path to this installed skill directory. Resolve it once per session. **Primary rule:** `<skill-dir>` is the directory containing this `SKILL.md`. That always works, regardless of how the skill was installed. The bundled detector is at `<skill-dir>/scripts/goversion/main.go`; the templates are at `<skill-dir>/assets/`. This skill ships a manifest for each supported harness (see the repo root), so it can be installed as a plugin on all of them. Each harness resolves the plugin root differently; use the row matching yours: | Harness | `<skill-dir>` resolution | |---|---| | Claude Code (plugin) | `${CLAUDE_PLUGIN_ROOT}/skills/go-ultimate` — the harness resolves this at runtime; the path includes a version directory, so do no...

Details

Author
Djarvur
Repository
Djarvur/go-ultimate
Created
2 months ago
Last Updated
3 days ago
Language
Go
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

golang-how-to

Route a Go engineering task across the available Go skills, explain overlaps, or design reusable project guidance. Use when the user asks which skills to apply, how to sequence a multi-concern workflow, or how to configure durable Go-specific agent instructions.

0 Updated yesterday
reagin
Code & Development Listed

golang-how-to

Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures the project's agent-config file (CLAUDE.md, AGENTS.md, GEMINI.md, Cursor rules, or Copilot instructions) to force-trigger skills in a project (/golang-how-to configure).

0 Updated 1 weeks ago
rzisso
AI & Automation Listed

author-skill

Author a new skill for this repo end to end — take a topic, check for existing coverage, drill the official docs behind it, write a filled handoff brief to docs/handoffs/, then draft the SKILL.md and run the post-draft checks. Use when asked to write, author, create, or scaffold a new skill, or when a drift-audit new-skill candidate has been accepted. Encodes this repo's own conventions rather than generic skill advice — verb naming for behavioral skills and fabric-/pbir-/pbid- prefixes for platform ones, the description as the entire trigger mechanism, long detail split into references/, lint-frontmatter.py, and which tree a new skill belongs in and its deploy step. Drills before it writes and never encodes an unverified claim. Ends at a linted draft plus a fresh-session test plan; writes no test fixtures and does not commit — fixtures and validation are test-skill's, which reads the brief back off disk. To fold a session learning into guidance that already exists, use learn instead.

1 Updated today
wardawgmalvicious