메뉴
Code coverage: thresholds and reporters for Vitest, Jest, pytest, Rust. Use when setting thresholds, adding Codecov/Coveralls, or wiring lcov/HTML reports.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-coverage명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-04-19T00:00:00.000Z" |
| reviewed | "2025-12-16T00:00:00.000Z" |
| description | Code coverage: thresholds and reporters for Vitest, Jest, pytest, Rust. Use when setting thresholds, adding Codecov/Coveralls, or wiring lcov/HTML reports. |
| allowed-tools | Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch |
| args | [--check-only] [--fix] [--threshold <percentage>] |
| argument-hint | [--check-only] [--fix] [--threshold <percentage>] |
| name | configure-coverage |
Check and configure code coverage thresholds and reporting for test frameworks.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up coverage thresholds for Vitest, Jest, pytest, or Rust | Running tests with coverage (/test:coverage) |
| Configuring coverage reporters (text, JSON, HTML, lcov) | Configuring the test framework itself (/configure:tests) |
| Adding Codecov or Coveralls integration to CI/CD | Analyzing test failures (test-runner agent) |
| Auditing coverage configuration compliance across a project | Writing individual test cases |
| Adjusting coverage threshold percentages | Configuring general CI/CD workflows (/configure:workflows) |
pwdfind . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \)find . -maxdepth 1 -name 'vitest.config.*'find . -maxdepth 1 -name 'jest.config.*'find . -maxdepth 1 -type d -name 'coverage'find . -maxdepth 1 \( -name 'codecov.yml' -o -name '.codecov.yml' \)find . -maxdepth 1 -name '.project-standards.yaml'Parse from command arguments:
--check-only: Report compliance status without modifications (CI/CD mode)--fix: Apply fixes automatically without prompting--threshold <percentage>: Set coverage threshold (default: 80)Default threshold: 80% (lines, branches, functions, statements)
Supported frameworks:
@vitest/coverage-v8 or @vitest/coverage-istanbul--coveragepytest-cov plugincargo-llvm-cov or cargo-tarpaulinExecute this code coverage compliance check:
Check for framework indicators:
| Indicator | Framework | Coverage Tool |
|---|---|---|
vitest.config.* with coverage | Vitest | @vitest/coverage-v8 |
jest.config.* with coverage | Jest | Built-in |
pyproject.toml [tool.coverage] | pytest | pytest-cov |
.cargo/config.toml with coverage | Rust | cargo-llvm-cov |
Use WebSearch or WebFetch to verify latest versions of coverage tools before configuring.
For the detected framework, check configuration completeness:
Vitest:
v8 or istanbul)text, json, html, lcov)Jest:
collectCoverage enabledcoverageProvider set (v8 or babel)collectCoverageFrom patterns configuredcoverageThresholds configuredcoverageReporters configuredpytest:
pytest-cov installed[tool.coverage.run] section exists[tool.coverage.report] section exists--cov-fail-under)Rust (cargo-llvm-cov):
cargo-llvm-cov installedPrint a formatted compliance report:
Code Coverage Compliance Report
================================
Project: [name]
Framework: [Vitest 2.x | pytest 8.x | cargo-llvm-cov 0.6.x]
Coverage Configuration:
Provider @vitest/coverage-v8 [CONFIGURED | MISSING]
Reporters text, json, html, lcov [ALL | PARTIAL]
Output directory coverage/ [CONFIGURED | DEFAULT]
Exclusions node_modules, dist, tests [CONFIGURED | INCOMPLETE]
Thresholds:
Lines 80% [PASS | LOW | NOT SET]
Branches 80% [PASS | LOW | NOT SET]
Functions 80% [PASS | LOW | NOT SET]
Statements 80% [PASS | LOW | NOT SET]
CI/CD Integration:
Coverage upload codecov/coveralls [CONFIGURED | MISSING]
Artifact upload coverage reports [CONFIGURED | MISSING]
Overall: [X issues found]
If --check-only, stop here.
Apply coverage configuration based on detected framework. Use templates from REFERENCE.md:
@vitest/coverage-v8, pytest-cov)Update .project-standards.yaml:
standards_version: "2025.1"
last_configured: "[timestamp]"
components:
coverage: "2025.1"
coverage_threshold: 80
coverage_provider: "[v8|istanbul|pytest-cov|llvm-cov]"
coverage_reporters: ["text", "json", "html", "lcov"]
coverage_ci: "codecov"
Print a summary of changes applied, scripts added, and next steps for verifying coverage.
For detailed configuration templates, see REFERENCE.md.
| Context | Command |
|---|---|
| Quick compliance check | /configure:coverage --check-only |
| Auto-fix all issues | /configure:coverage --fix |
| Custom threshold | /configure:coverage --fix --threshold 90 |
| Check coverage config exists | find . -maxdepth 1 -name 'vitest.config.*' -o -name 'jest.config.*' 2>/dev/null |
| Verify coverage directory | test -d coverage && echo "EXISTS" |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--threshold <percentage> | Set coverage threshold (default: 80) |
# Check compliance and offer fixes
/configure:coverage
# Check only, no modifications
/configure:coverage --check-only
# Auto-fix with custom threshold
/configure:coverage --fix --threshold 90
/configure:tests first/configure:tests - Configure testing frameworks/test:coverage - Run tests with coverage/configure:all - Run all compliance checksInstall, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.