verify
Use before claiming work is complete, before committing, or before creating a PR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use before claiming work is complete, before committing, or before creating a PR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | verify |
| description | Use before claiming work is complete, before committing, or before creating a PR. |
Run these before saying "done." No exceptions.
Type check — bun tsc
as any to silence errors — fix the typesTests — bun test
tests/ mirroring src/ structureSmoke test — run the actual thing
bun run ra --provider <name> "Hello"bun run ra "Use <tool> to ..."bun run ra --skill <name> "Test prompt"cd recipes/<name> && ra --config ra.config.yaml "test prompt"Review diff — git diff
as any castsbun testbun tsc ("it runs" != "it type-checks")console.log debugging statements inSystem design and architecture decisions. Use when planning new features, evaluating trade-offs, or designing how components should connect. Proposes 2-3 approaches and recommends one.
Smart commit workflow. Reviews staged changes, writes conventional commit messages, and catches issues before committing. Use when ready to commit work.
Quality review of completed work. Use after making changes and before claiming completion. Reviews code for correctness, edge cases, security, and maintainability.
Systematic debugging workflow. Use when diagnosing bugs, test failures, or unexpected behavior. Follows a rigorous reproduce → isolate → hypothesize → fix → verify cycle.
Systematic multi-agent research. Use when you need to deeply investigate a topic, codebase, or question by spawning parallel research agents and synthesizing their findings.
Deep code explanation. Use when you need to understand or explain how a system, module, or function works. Traces data flow, maps dependencies, and explains design decisions.