Go Skills Router

This repository publishes 35 Go skills. Their triggers necessarily overlap — "this is slow" could be performance, concurrency, database, or a leak. Use the tables below to pick the owner, then load the secondary skills in the same pass rather than discovering them one at a time.

This is an index. Every skill it names stands alone and can be read without this one.

Routing Table

Boundaries Between Overlapping Skills

Load the one that owns the question being asked, not the one that matches a keyword in the code.

"It is slow."

• go-performance-review — the code allocates or copies too much. Owns benchmarks, pprof, and optimisation patterns.
• go-concurrency-review — the code contends on a lock or serialises work that could run in parallel.
• go-database — the query is the problem: missing index, N+1, pool exhaustion.
• go-troubleshooting — you do not yet know which of the three it is. Start here to find out, then hand off.

"It crashed."

• go-troubleshooting — a panic, deadlock, or leak already happened. Diagnosis, profiles, delve.
• go-defensive-coding — prevention. Nil traps, aliasing, overflow, the constructs that make the next crash impossible.
• go-concurrency-review — a data race or a goroutine lifecycle bug.

"Is this secure?"

• go-security-audit — external threats: injection, auth, secrets, TLS.
• go-dependency-audit — known CVEs in modules you import.
• go-defensive-coding — internal correctness bugs that are not attacks.

"How should this be structured?"

• go-architecture-review — the shape of an existing codebase.
• go-project-layout — the shape of a new one.
• go-interface-design — the shape of one type or contract.
• go-refactoring — the process of getting from the current shape to the target shape. Load it alongside whichever skill above owns that target.

"How do I expose this?"

• go-api-design — HTTP/REST handlers, routing, middleware, idempotency, health checks, shutdown.
• go-openapi — the contract is a spec and code is generated from it.
• go-graphql — the client picks the shape of the response.
• go-grpc — protobuf contract, interceptors, streaming.

"Tests."

• go-test-quality — what to test, how to isolate it, what to mock, synctest, goleak, benchmarks.
• go-test-table-driven — the table pattern specifically: when it helps, how to shape the case struct, when to stop using it.

"Style."

• go-coding-standards — the rules the code should follow.
• go-naming — what things are called: packages, types, functions, receivers, errors.
• go-code-review — applying rules to someone else's change, with severity.
• go-modernize — rules that changed because the language moved.
• go-ci — making a machine enforce them.

"Ship it."

• go-ci — the pipeline that gates every change: build, lint, test, scan.
• go-build-release — turning a tag into signed, reproducible artifacts.
• go-binary-size — making those artifacts smaller.

Which Tool Answers the Question

Multi-Concern Tasks

A real task usually crosses three skills. Load them together at the start rather than sequentially.

Configure a Project to Use These Skills

Asked to make a project load these skills automatically:

1. Find the agent-config files the project already has: CLAUDE.md, AGENTS.md, GEMINI.md, .github/copilot-instructions.md, .cursor/rules/.
2. Skip any file that already references go-skills-router.

3. Propose this block for each, show the diff, and write only after the developer agrees:

   ## Go skills
   
   Before any Go coding, review, debugging or setup task, consult the
   `go-skills-router` skill and load the skills it names for the task.

4. If the team wants some skills on every task regardless of routing (for example go-error-handling and go-security-audit), list them under the block as "Always load", with the reason.

Full Catalogue

Verification Checklist

1. The primary skill matches the question being asked, not a keyword in the code
2. Secondary skills were loaded in the same pass, not discovered one at a time
3. For a diagnosis task, go-troubleshooting ran before an optimisation skill
4. For a restructuring task, go-refactoring was paired with the skill owning the target shape
5. If exactly one skill applies, it was loaded directly without routing
6. Project configuration written only after the developer approved the diff