Write idiomatic, production-grade Go. Self-contained — all rules inline, no reference files. Use when editing .go files, go.mod, go.sum, or Go tests, or when asked to design, generate, or review Go code. Covers style, control flow, errors, concurrency, context, testing, performance, security, modules, JSON, database…
Produce a structured implementation plan document and save it to disk. Use when asked to write, create, or generate an implementation plan for a feature or change.
Implement a plan written by the plan-doc skill (.agents/plans/.md) on its feature branch, one commit per logical change. Use only when explicitly asked to implement, execute, or carry out such a plan.
Review a plan doc written by the plan-doc skill with multiple AI agents, verify their findings, and apply the verified fixes to the plan file in place. Use when asked to review, audit, or critique a plan written by plan-doc.
Go 1.24+ development workflow with TDD, quality gates, and code review. Provides specialized agents, skills, and commands for professional Go development.
★not rated 2 7mo agoA
tokens not measured
originalMIT
Stepped git flow — create a feature branch, commit staged changes, then push and open a PR. Run all steps or select a subset by number or name (branch, commit, pr).
Default-branch resolution, branch naming and creation, Conventional Commits, commit hygiene, and push, pull request, and attribution rules. Use before creating a branch, committing, pushing, or opening a pull request.
Shared protocol for fanning a review out to the ask-agent agents — prompt file, background launch, response classes, the orchestrator's own review, verification and merging, coverage, and cleanup. Load only when a review skill (multi-code-review, plan-review) says to.
★not rated 2 20d agoA61 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: