원클릭으로
coverage
Run tests with coverage analysis and identify untested code paths. Use to find gaps before releases.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Run tests with coverage analysis and identify untested code paths. Use to find gaps before releases.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | coverage |
| description | Run tests with coverage analysis and identify untested code paths. Use to find gaps before releases. |
| disable-model-invocation | true |
| argument-hint | package-path |
Run Go tests with coverage profiling to identify untested code paths.
/coverage - Coverage for all packages/coverage ./internal/repo/... - Coverage for specific packageRun tests with coverage
If $ARGUMENTS specifies a package:
go test -coverprofile=coverage.out -covermode=atomic -timeout 5m $ARGUMENTS 2>&1
Otherwise, run all packages:
go test -coverprofile=coverage.out -covermode=atomic -timeout 5m ./... 2>&1
Generate coverage summary
go tool cover -func=coverage.out 2>&1
Identify low-coverage packages
Parse the output and flag packages below 50% coverage.
Report findings
## Coverage Results
### Package Summary
| Package | Coverage | Status |
|---------|----------|--------|
### Overall
- Total coverage: N%
### Low Coverage (< 50%)
- [packages needing attention]
### Uncovered Functions
- [key uncovered functions in critical packages]
Cleanup
rm -f coverage.out
Pay special attention to coverage in:
internal/repo/ - Data access layerinternal/manager/ - Orchestration logicinternal/index/ - Search indexinginternal/search/ - Search API handlersgo tool cover -html=coverage.out -o coverage.html-tags integration and Docker_test.go) are excluded from coverage automaticallyRun Go benchmarks and compare results to detect performance regressions. Use before and after performance-related changes.
Run pre-push quality checks (vet + lint + tests with race detector). Use before pushing code.
Check and tidy Go module dependencies. Use after adding/removing imports or before releases.
Run go generate to build templ templates and frontend assets. Use after changing templates or CSS/JS.
Run integration tests that require Docker (Postgres, MinIO via testcontainers). Use to validate database and storage behavior.
Run golangci-lint and static analysis on Go code. Use before pushing or to check code quality.