Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From write-go-code
Go code style guide based on Google Go Style Guide, Effective Go, and Code Review Comments. Use when: (1) writing new Go code, (2) reviewing Go code for style compliance, (3) refactoring existing Go code, (4) conducting code reviews. Covers naming, error handling, concurrency, testing, data types, functions, interfaces, code organization, and Cobra CLI command behavior.
How this skill is triggered — by the user, by Claude, or both
Slash command
/write-go-code:write-go-codeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Clarity over cleverness** - Code should be obvious to readers
references/comprehensive/cobra.mdreferences/comprehensive/code-organization.mdreferences/comprehensive/concurrency.mdreferences/comprehensive/data-types.mdreferences/comprehensive/errors.mdreferences/comprehensive/functions.mdreferences/comprehensive/interfaces.mdreferences/comprehensive/makefile-conventions.mdreferences/comprehensive/naming.mdreferences/comprehensive/testing.mdreferences/essential/checklist.mdmake lint, make fmt or gofmt, goimports)references/essential/checklist.mdreferences/comprehensive/{topic}.mdreferences/comprehensive/cobra.mdQuick reviews (default):
references/essential/checklist.md - Condensed, actionable rulesDeep dives by topic:
references/comprehensive/naming.md - Package names, identifiers, receiversreferences/comprehensive/errors.md - Error handling, panic/recoverreferences/comprehensive/concurrency.md - Goroutines, channels, contextreferences/comprehensive/testing.md - Test quality and patternsreferences/comprehensive/code-organization.md - Imports, packages, structurereferences/comprehensive/data-types.md - new vs make, slices, mapsreferences/comprehensive/functions.md - Multiple returns, deferreferences/comprehensive/interfaces.md - Embedding, type assertionsreferences/comprehensive/makefile-conventions.md - Required CI targets, fmt vs formatreferences/comprehensive/cobra.md - Cobra root command usage templatesGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
npx claudepluginhub cboone/agent-harness-plugins --plugin write-go-code