cc-go-dev

Applies idiomatic Go conventions for package structure, error handling, concurrency, and testing.

1.0k|109|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill cc-go-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-go-dev
Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-go-dev
Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-go-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Go codebases often drift into inconsistent package boundaries, swallowed errors, unsafe goroutines, and missing tests. This Skill gives the AI a focused set of Go development conventions so edits and reviews of Go source code stay idiomatic and safe.

Core Features & Use Cases

  • Idiomatic Go Guidance: Enforces simple, explicit implementations with clear package boundaries and naming conventions.
  • Error Handling Discipline: Requires errors to be handled with context, using %w wrapping and errors.Is/errors.As for branching.
  • Concurrency & Testing Rules: Covers goroutine lifecycle management with context.Context, race detection via go test -race, and table-driven tests.
  • Use Case: When asking the AI to add a new endpoint to a Go service, it will structure the handler, wrap errors with context, manage goroutine cancellation properly, and add table-driven tests for affected logic.

Quick Start

Ask the AI to review or modify your Go source files while following the cc-go-dev conventions for package structure, error handling, concurrency, and testing.

Frequently Asked Questions about cc-go-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Go error handling best practices in AI-assisted coding?

This Skill instructs the AI to never ignore errors, to add context when returning them, to wrap with %w when appropriate, and to use errors.Is or errors.As for branching logic. These rules are detailed in the errors reference document.

What Go concurrency rules should AI follow when writing goroutines?

The Skill requires deciding who waits for and who cancels each goroutine before starting it, preferring context.Context for lifecycle control, defining synchronization strategy for shared state, and considering go test -race for race detection.

When should I not use this Go development skill?

Do not use it for formal code review or fix/debug workflows, operational risk assessment, or general change boundaries unrelated to Go. It is scoped specifically to writing and editing idiomatic Go source code.

How does the skill handle Go project structure decisions?

It keeps entry points, business logic, data access, and model boundaries clear, only extracts shared code when cross-boundary reuse is genuinely justified, and splits files within a package by responsibility rather than meaningless names.

What testing approach does this skill recommend for Go code?

It prioritizes adding local tests for affected logic, prefers table-driven tests with clear naming, and recommends race detection when concurrency guarantees are needed.