메뉴
Run tests with coverage and report uncovered lines/branches per class. Use when user wants to check test coverage, find untested code, identify coverage gaps, or mentions /test-coverage command. Also use after green phases to verify new code is well-covered.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Review the latest work unit with fresh, unnarrowed eyes and surface any problem it contains as follow-ups. Use after a work-unit commit, or when the user runs /agent-review.
Continue working on a story or task by reading progress.md, executing the next work unit, and updating progress. Use when user wants to resume story/task work or mentions /continue command.
Run a Selenium test in visible (non-headless) mode with slowdown so the user can watch it. Use when user wants to demo or visually watch a Selenium test or mentions /demo command.
Preview the planned design for a scenario before writing tests. Shows domain model changes, usecase patterns, and key design choices. Use before red-usecase to get user approval on the implementation approach. If the user rejects the design, offers to discuss inline or escalate to /architecture for a full ADR.
Write a journey summary capturing noteworthy moments (predictions, decisions, surprises, mistakes, quirks). Runs automatically the moment the agent observes something worth noting during work, and manually before /clear or /compact as a final sweep. Idempotent — skips entries already recorded. Use when the agent observes a noteworthy moment, before clearing context, or when the user mentions /handoff.
Re-explain the last thing in plain words. Use ONLY when the user explicitly types /plain or asks to "explain that simply / in plain words / like I'm not an expert". Never invoke on your own initiative — this is a manual button the user presses when something was hard to follow.
| name | test-coverage |
| description | Run tests with coverage and report uncovered lines/branches per class. Use when user wants to check test coverage, find untested code, identify coverage gaps, or mentions /test-coverage command. Also use after green phases to verify new code is well-covered. |
/test-coverage usecase
/test-coverage h2
/test-coverage rest RegisterUserController
/test-coverage usecase --focus # only classes touched in recent git diff
First word is the module:
usecase → :usecaseh2, rest, email, scheduling, security → :adapters:{name}domain → :domainOptional second word filters the report to classes matching that name.
Optional --focus flag restricts the report to classes changed since the last commit (useful after a green phase to check only new code).
Delegate to .claude/agents/coverage-agent.md which loads .claude/tech/{backend}/templates/testing/coverage-commands.md for commands, report format, gap mapping, and remediation.
Steps:
--focus mode: map gaps to scenarios, classify reachability, update progress.md with red/green steps for reachable gaps, flag dead code for refactor.claude/agents/coverage-agent.md — workflow for gap analysis, reachability classification, progress.md updates.claude/templates/testing/coverage-commands.md — universal workflow: focus mode, module mapping, report format.claude/tech/{backend}/templates/testing/coverage-commands.md — tool-specific commands: run, parse, extract