How do I install the Write Go Code skill?

Run npx skillmds@latest add cboone/write-go-code in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Write Go Code safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write Go Code?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Write Go Code free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Write Go Code?

cboone (@cboone) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Write Go Code by cboone — Agent Skill

Name: Write Go Code
Author: cboone

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.

cboone 078f6e8 12 files · 43.1 KB Updated Sep 17, 2026

File contents

Write Go Code

Core Principles

Clarity over cleverness - Code should be obvious to readers
Simplicity - Accomplish goals in the most straightforward way
Consistency - Match surrounding code and project conventions
Minimal indentation - Handle errors early, keep happy path unindented

Workflow

Run automated checks (make lint, make fmt or gofmt, goimports)
Review against essential checklist: references/essential/checklist.md
For specific questions, consult: references/comprehensive/{topic}.md
When creating or editing Cobra root commands, consult: references/comprehensive/cobra.md

Reference Navigation

Quick reviews (default):

references/essential/checklist.md - Condensed, actionable rules

Deep dives by topic:

references/comprehensive/naming.md - Package names, identifiers, receivers
references/comprehensive/errors.md - Error handling, panic/recover
references/comprehensive/concurrency.md - Goroutines, channels, context
references/comprehensive/testing.md - Test quality and patterns
references/comprehensive/code-organization.md - Imports, packages, structure
references/comprehensive/data-types.md - new vs make, slices, maps
references/comprehensive/functions.md - Multiple returns, defer
references/comprehensive/interfaces.md - Embedding, type assertions
references/comprehensive/makefile-conventions.md - Required CI targets, fmt vs format
references/comprehensive/cobra.md - Cobra root command usage templates

Sources

---name: write-go-codedescription: 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.---# Write Go Code## Core Principles1. **Clarity over cleverness** - Code should be obvious to readers1. **Simplicity** - Accomplish goals in the most straightforward way1. **Consistency** - Match surrounding code and project conventions1. **Minimal indentation** - Handle errors early, keep happy path unindented## Workflow1. Run automated checks (`make lint`, `make fmt` or `gofmt`, `goimports`)1. Review against essential checklist: `references/essential/checklist.md`1. For specific questions, consult: `references/comprehensive/{topic}.md`1. When creating or editing Cobra root commands, consult: `references/comprehensive/cobra.md`## Reference Navigation**Quick reviews (default):**- `references/essential/checklist.md` - Condensed, actionable rules**Deep dives by topic:**- `references/comprehensive/naming.md` - Package names, identifiers, receivers- `references/comprehensive/errors.md` - Error handling, panic/recover- `references/comprehensive/concurrency.md` - Goroutines, channels, context- `references/comprehensive/testing.md` - Test quality and patterns- `references/comprehensive/code-organization.md` - Imports, packages, structure- `references/comprehensive/data-types.md` - new vs make, slices, maps- `references/comprehensive/functions.md` - Multiple returns, defer- `references/comprehensive/interfaces.md` - Embedding, type assertions- `references/comprehensive/makefile-conventions.md` - Required CI targets, fmt vs format- `references/comprehensive/cobra.md` - Cobra root command usage templates## Sources- [Effective Go](https://go.dev/doc/effective_go)- [Google Go Style Guide](https://google.github.io/styleguide/go/)- [Go Code Review Comments](https://go.dev/wiki/CodeReviewComments)

Frequently asked questions

Write Go Code

File contents

Write Go Code

Core Principles

Workflow

Reference Navigation

Sources

Related skills

Frequently asked questions

How do I install the Write Go Code skill?

What does the Write Go Code skill do?

Is Write Go Code safe to use?

Which AI agents work with Write Go Code?

Is Write Go Code free to use?

Who published Write Go Code?