메뉴
Query and analyze test coverage. Use this to check coverage before modifying code, identify uncovered files before a PR, or track coverage trends over time. Triggers immediately on keywords like "coverage", "test pass", "uncovered areas", or "add tests".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Cross-project experience memory — your persistent knowledge base across sessions. Remembers what worked, what failed, and why, so every new session starts smarter. Log outcomes → recall lessons → apply patterns. Use when starting work that other projects have solved, when you need to avoid past mistakes, or when onboarding to a new project area. Also logs skill execution outcomes to improve future routing. Responds to: 'memento', 'cross-project knowledge', 'what did we learn', 'past experience', 'avoid repeating', 'session memory', 'global memory', '스킬 성능', '스킬 추천', '스킬 건강', '어떤 스킬이 좋아'.
cmux 창 분할 기반 멀티-AI 합의 리뷰 엔진. 동일 워크스페이스에서 Gemini/Codex 패널을 나란히 분할해 3-Stage 파이프라인(의견 → 반론 → 합성)을 진짜 병렬로 실행합니다. multi-ai-review의 순차 실행 대신 두 AI가 동시에 리뷰하는 것을 실시간으로 볼 수 있음. "/cmux-ai-review", "cmux 코드 리뷰", "AI 패널 리뷰", "병렬 리뷰" 등 cmux 환경에서 여러 AI의 동시 리뷰가 필요한 요청이라면 반드시 이 스킬을 사용하세요.
Claude + Gemini CLI + Codex CLI multi-AI consensus engine. 3-Stage Pipeline (opinions → rebuttal → synthesis) drives consensus across domains: code review, market analysis, investment diligence, risk assessment, and more. Automatically detects domain from natural language and applies appropriate preset. Triggers: - "review this", "convene a council", "get multiple AI opinions", "deep review", "consensus" - "market analysis", "macro analysis", "investment review", "risk assessment" - Any situation needing multiple perspectives — trigger proactively
Routes each agent role to the optimal AI model (Claude/Gemini/Codex) and executes it. Automatically assigns Codex for code writing, Gemini for design, and Claude for planning and orchestration. Use this skill whenever you see "use Codex for code", "use Gemini for design", "use a different AI", or "model routing" requests. Triggers on /multi-ai-run.
Comprehensive quality audit before phase completion or deployment. Performs planning conformance, DDD validation, security checks, tests, browser verification, and quantitative metrics. Also enforces verification-before-completion discipline — no claims without evidence. Run this skill before deploying, before merging a PR, after completing significant changes, and whenever anyone claims 'it works' or 'tests pass'. Triggers immediately on 'quality check', 'pre-deploy check', 'audit this', 'QA', 'verify this', 'does this work', '품질 검사', '배포 전 검사'. Trigger: /audit, /evaluate, /verify.
cmux 창 분할 기반 멀티-AI 병렬 태스크 실행. 동일 워크스페이스에서 Codex(코드)/Gemini(디자인)/Claude(계획)를 패널로 분할해 동시에 실행합니다. multi-ai-run의 순차 실행과 달리 진짜 병렬. "/cmux-ai-run", "cmux로 AI 분업", "창 분할 병렬 실행", "codex gemini 동시 실행" 등 cmux 환경에서 여러 AI를 동시에 돌리고 싶은 요청이라면 반드시 이 스킬을 사용하세요.
| name | coverage |
| description | Query and analyze test coverage. Use this to check coverage before modifying code, identify uncovered files before a PR, or track coverage trends over time. Triggers immediately on keywords like "coverage", "test pass", "uncovered areas", or "add tests". |
| version | 2.3.0 |
| updated | "2026-03-12T00:00:00.000Z" |
Purpose: Query test coverage, identify uncovered areas, and track coverage trends.
Role breakdown:
Skill Timing Scope /coverage(this skill)Before/after changes, regular queries Coverage status + uncovered areas + trends /auditBefore deployment Full audit /impactBefore changes Impact analysis
1. Detect project type (Python/Node.js/Rust/Go, etc.)
2. Check test environment
3. Collect coverage data
4. Identify uncovered files/areas
5. Analyze coverage trends (when available)
6. Generate report and present recommendations
| Command | Description |
|---|---|
/coverage | Full project coverage query |
/coverage <path> | Coverage for a specific directory/file |
/coverage --uncovered | Show only uncovered areas |
/coverage --threshold <n> | Show files below n% coverage |
/coverage --trend | Coverage trend (7-day/30-day) |
/coverage --function <file> | Per-function coverage for a file |
/coverage --branch | Detailed branch coverage |
/coverage --report | Generate detailed HTML report |
ls pyproject.toml setup.py requirements.txt 2>/dev/null && echo "Python"
ls package.json 2>/dev/null && echo "Node.js"
ls Cargo.toml 2>/dev/null && echo "Rust"
ls go.mod 2>/dev/null && echo "Go"
| Project | Command |
|---|---|
| Python | pytest --cov=. --cov-report=json --cov-report=term-missing |
| Node.js (Vitest) | npm run test -- --coverage |
| Node.js (Jest) | npm run test -- --coverage |
| Rust | cargo tarpaulin --out Json |
| Go | go test -coverprofile=coverage.out ./... |
From the coverage report, identify:
| Coverage | Verdict | Action |
|---|---|---|
| 80%+ | Good | Maintain this level during maintenance |
| 70–80% | Improve | Add exception/edge case tests |
| Below 70% | Low | Run /coverage --uncovered to identify gaps, then add tests |
| Skill | When to Link | Purpose |
|---|---|---|
/impact <file> | Before a change | Check coverage after impact analysis |
/audit | Before deployment | Coverage validation within full audit |
/checkpoint | On task completion | Coverage check during code review |
For detailed output examples, per-language configuration, and usage scenarios, see:
references/output-formats.md — Output format detailsreferences/tech-specs.md — Per-language test runner configurationreferences/scenarios.md — Usage scenarios and integration examplesLast Updated: 2026-03-12 (v2.3.0 - Progressive Disclosure applied)