golang-testing
Provides a comprehensive guide for writing production-ready Golang tests. Covers table-driven tests, test suites with testify, mocks, unit tests, integration tests, benchmarks, code coverage, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, memory leaks, CI with GitHub Actions, and idiomatic naming conventions. Use this whenever writing tests, asking about testing patterns or setting up CI for Go projects. Essential for ANY test-related conversation in Go.
83
86%
Does it follow best practices?
Impact
69%
1.53xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that thoroughly enumerates specific capabilities, includes abundant natural trigger terms, and explicitly states both what the skill does and when to use it. The only minor concern is that the description is quite long and could be slightly more concise, but the verbosity is justified by the breadth of topics covered. The third-person voice is used correctly throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists numerous specific concrete actions and topics: table-driven tests, test suites with testify, mocks, unit tests, integration tests, benchmarks, code coverage, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, memory leaks, CI with GitHub Actions, and naming conventions. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide covering table-driven tests, mocks, benchmarks, CI, etc.) and 'when' with explicit triggers ('Use this whenever writing tests, asking about testing patterns or setting up CI for Go projects. Essential for ANY test-related conversation in Go.'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'tests', 'testing patterns', 'Go', 'Golang', 'CI', 'mocks', 'benchmarks', 'code coverage', 'fuzzing', 'GitHub Actions'. These are all terms users would naturally use when asking about Go testing. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Go/Golang testing specifically, with distinct triggers like 'Golang', 'Go projects', 'testify', 'goleak', and 'GitHub Actions' for CI. This is unlikely to conflict with testing skills for other languages or general Go development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, comprehensive Go testing skill with strong actionability and excellent progressive disclosure. The code examples are executable and cover the major testing patterns. Minor weaknesses include some verbosity in explanations of concepts Claude already knows and a lack of explicit validation checkpoints in the workflow modes.
Suggestions
Trim explanatory text that Claude already knows (e.g., 'Unit tests should be fast, isolated, and deterministic', 'Use fuzzing to find edge cases and bugs') to improve conciseness.
Add explicit validation/verification steps to the Write and Audit modes — e.g., 'After generating tests, run `go test -race ./...` and verify no failures before proceeding to edge cases.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but includes some unnecessary explanations Claude would already know (e.g., 'Unit tests should be fast (< 1ms), isolated (no external dependencies), and deterministic', explaining what fuzzing does). The best practices summary is useful but some items are basic Go knowledge. The synctest section's explanation of key differences is somewhat verbose. | 2 / 3 |
Actionability | Excellent executable code examples throughout — table-driven tests, goleak setup, benchmarks, parallel tests, fuzzing, examples as documentation, integration tests with build tags, and a comprehensive quick reference of CLI commands. All code is copy-paste ready and complete. | 3 / 3 |
Workflow Clarity | The modes section (Write/Review/Audit/Debug) provides good high-level workflow guidance, and the best practices are clearly numbered. However, there are no explicit validation checkpoints or feedback loops for multi-step processes like writing tests, reviewing PRs, or auditing test suites. The Debug mode mentions sequential steps but lacks concrete validation gates. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with clear one-level-deep references to separate files (HTTP Testing, Mocking, Integration Testing, Helpers) and cross-references to other skills (golang-benchmark, golang-linter, golang-stretchr-testify, etc.). The main file serves as a well-organized overview with inline essentials and pointers to detailed materials. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- samber/cc-skills-golang
- Commit
b88f91d
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.