test
Run Go unit tests. Use after code changes to verify correctness.
Best use case
test is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run Go unit tests. Use after code changes to verify correctness.
Teams using test should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/test/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How test Compares
| Feature / Agent | test | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run Go unit tests. Use after code changes to verify correctness.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Run Unit Tests Run Go unit tests with optional package targeting and verbose output. ## Usage - `/test` - Run all unit tests - `/test ./internal/repo/...` - Run tests in specific package - `/test -v ./internal/manager/...` - Verbose output ## Steps 1. **Run tests** If `$ARGUMENTS` specifies a package, use that: ```bash go test -timeout 5m $ARGUMENTS 2>&1 ``` Otherwise, run all packages: ```bash go test -timeout 5m ./... 2>&1 ``` 2. **Parse results** Report: ``` ## Test Results ### Passed - [list of passed tests] ### Failed - [list of failed tests with error details] ### Summary - Total: N | Passed: N | Failed: N | Skipped: N - Duration: Ns ``` 3. **On failure**, read the failing test and corresponding source files to understand the failure, then suggest a fix. ## Tips - Use `-v` for verbose output when debugging specific test failures - Use `-run TestName` to run a single test - Use `-short` to skip long-running tests during iteration - For race detection, use `/race-check` instead - For integration tests (testcontainers), use `/integration-test` instead
Related Skills
integration-test
Run integration tests that require Docker (Postgres, MinIO via testcontainers). Use to validate database and storage behavior.
security-scan
Run gosec and govulncheck to find security vulnerabilities. Use before releases or after dependency changes.
reindex
Trigger reindexing of a specific WordPress extension. Use to rebuild the search index for a plugin, theme, or core version.
race-check
Run Go race detector to find data races in concurrent code. Use after any change to mutexes, goroutines, or channels.
profile
Run CPU and memory profiling with pprof to identify performance hotspots. Use when investigating high resource usage.
migrate
Create and manage database migrations using goose. Use for schema changes, new tables, or index optimization.
lint
Run golangci-lint and static analysis on Go code. Use before pushing or to check code quality.
generate
Run go generate to build templ templates and frontend assets. Use after changing templates or CSS/JS.
deps
Check and tidy Go module dependencies. Use after adding/removing imports or before releases.
coverage
Run tests with coverage analysis and identify untested code paths. Use to find gaps before releases.
check
Run pre-push quality checks (vet + lint + tests with race detector). Use before pushing code.
benchmark
Run Go benchmarks and compare results to detect performance regressions. Use before and after performance-related changes.