メニュー
Run Go unit tests, coverage reports, and benchmarks. Use when you need to run tests, check coverage, run benchmarks, or regenerate mocks after interface changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Develop CLI applications in Go. Use when creating or modifying CLI commands, adding flags or arguments, implementing command workflows, building interactive prompts, handling signals and exit codes, or working with stdin/stdout/stderr. Currently uses Cobra for command structure and Huh for interactive UI.
Build Go binaries for local development or release. Use when you need to compile the project, troubleshoot build failures, or understand the build pipeline.
Lint and format Go code. Use when you need to run linters, fix lint errors, format code, or understand why a linter is complaining.
Apply Go coding standards when writing or modifying Go code. Use when implementing functions, using dependency injection, handling errors idiomatically, or working with interfaces. For test conventions, use the `writing-go-tests` skill instead.
Write Go tests following project conventions. Use when creating test files, writing unit or integration tests, choosing mocks, or setting up test fixtures. Covers test naming, assertions, mock usage, table-driven patterns, and common pitfalls.
| name | testing-go-code |
| description | Run Go unit tests, coverage reports, and benchmarks. Use when you need to run tests, check coverage, run benchmarks, or regenerate mocks after interface changes. |
All commands run from the Go module root (cova/).
task test # Run all tests with race detection
task test -- -run TestName # Run specific test(s)
task test -- -short # Skip integration tests
For test conventions (naming, assertions, table-driven patterns, mock usage), see the writing-go-tests skill.
task cov
Runs tests with coverage and opens an HTML report in the browser.
task bench
Runs all benchmarks with memory allocation stats.
task check
Runs tests + lint in sequence. Use before committing.
mockery
Run from the module root with no arguments after adding or modifying interfaces. Configuration is in .mockery.yml.
NEVER edit generated mock files (*_mock.go) manually. Always regenerate with mockery. This applies to all mock changes — adding parameters, renaming methods, updating signatures, fixing imports. No exceptions.
mockery fails due to stale mocksStale mock files frequently cause mockery to fail (e.g., type conflicts from old signatures). When this happens:
*_mock.go file(s)mockeryDo NOT attempt to fix the mock file by hand — delete and regenerate.