메뉴
Write tests or LLM evals. Routes to a specialist: the test-writer agent for code tests (unit/integration), the eval-writer agent for AI/LLM evals (--eval). Use after implementing a feature, when coverage is low, or when building/ changing an LLM-powered feature.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Design system architecture and decompose work into Acts with tasks, dependencies, and cycle budgets. Use after a spec is approved, before coding begins.
Review, test, slop-check, then commit and optionally open a PR. The ship pipeline: one command from "code complete" to "committed and reviewed."
Show all UV Suite skills, agents, hooks, guardrails, and personas. Use when you want to know what's available or how to use a specific feature.
Systematic root-cause debugging. Traces data flow, tests hypotheses, narrows scope. Stops after 3 failed attempts and escalates. Use when something is broken and you don't know why.
Toggle lite mode — instructs the assistant to be terse (no preamble, no summaries, no decorative formatting). Use when tokens are limited or you just want shorter answers. Persists across turns until disabled.
Build an interactive prototype as a static React site. For concept exploration, stakeholder demos, presentations, and documentation websites.
SOC 직업 분류 기준
| name | uvs-test |
| description | Write tests or LLM evals. Routes to a specialist: the test-writer agent for code tests (unit/integration), the eval-writer agent for AI/LLM evals (--eval). Use after implementing a feature, when coverage is low, or when building/ changing an LLM-powered feature. |
| argument-hint | [target] [--unit|--integration|--eval] |
| user-invocable | true |
| context | fork |
| model | claude-opus-4-6 |
| effort | high |
| allowed-tools | ["Read(*)","Grep(*)","Glob(*)","Agent(*)"] |
$ARGUMENTS
The orchestrator picks one specialist per run. Default is --unit.
case "$ARGUMENTS" in
*--eval*) echo "MODE=eval → specialists/eval.md (eval-writer agent)";;
*--integration*) echo "MODE=integration → specialists/integration.md (test-writer agent)";;
*) echo "MODE=unit → specialists/unit.md (test-writer agent)";;
esac
!find . \( -name "*.test.*" -o -name "*.spec.*" -o -name "test_*" \) -not -path "*/node_modules/*" 2>/dev/null | head -5
!cat $(find . \( -name "*.test.*" -o -name "*.spec.*" \) -not -path "*/node_modules/*" 2>/dev/null | head -1) 2>/dev/null | head -40 || echo "No existing tests found"
!cat package.json 2>/dev/null | grep -A2 '"test"' || echo "No package.json test script"
!find . \( -name "*eval*" -o -name "*evals*" \) -not -path "*/node_modules/*" 2>/dev/null | head -10 || echo "No eval files found"
Write eval artifacts under this directory (scoped to the current session):
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-session.sh
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh 'specs/*.md' 60 || echo "No spec found — work from code/prompt behavior"
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh 'architecture/acts-plan.md' 40 || echo "No acts plan found"
!cat uv-out/current/checkpoints/latest.md 2>/dev/null | head -40 || echo "No checkpoint"
Read the MODE line above. It names the specialist prompt file and the agent to use:
| MODE | Specialist prompt | Agent |
|---|---|---|
| unit | skills/uvs-test/specialists/unit.md | test-writer |
| integration | skills/uvs-test/specialists/integration.md | test-writer |
| eval | skills/uvs-test/specialists/eval.md | eval-writer |
You (the orchestrator) read the matching specialist prompt at
.claude/skills/uvs-test/specialists/<mode>.md, then dispatch the named agent via the Agent
tool, passing the specialist prompt content + the target ($ARGUMENTS) + the gathered
context above as the agent's task. Do not write the tests or evals yourself — the agent does.
Relay the agent's result. If $ARGUMENTS names no target, ask what to test.