メニュー
Use when dispatching spec-compliance or code-quality reviewer subagents, before writing the reviewer prompt. Ensures reviewers run tests and typecheck instead of only reading code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | verified-reviews |
| description | Use when dispatching spec-compliance or code-quality reviewer subagents, before writing the reviewer prompt. Ensures reviewers run tests and typecheck instead of only reading code. |
Reviewer subagents MUST run the project's test suite and typecheck as part of every review. Reading code alone is insufficient — it misses runtime failures, type errors, and regressions.
Every reviewer subagent prompt MUST include these verification steps:
## Required Verification (Non-Negotiable)
Before forming your assessment, you MUST run:
1. `npm test` — full test suite must pass
2. `npm run typecheck` — no type errors
If either fails, report ❌ immediately with the failure output.
Do NOT approve code that you haven't verified passes tests and typecheck.
Do NOT skip these because "the implementer said tests pass."
Implementers report "all tests pass" but may have:
If you catch yourself thinking any of these, STOP:
| Thought | Reality |
|---|---|
| "The implementer already ran tests" | Trust but verify. Run them yourself. |
| "I can tell from reading the code" | You can't detect runtime regressions by reading. |
| "Running tests is the implementer's job" | Verification is the reviewer's job. |
| "The diff looks clean" | Clean diffs can still break things. |
Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.
Use when changing console logging in this repo. Prefer console.info for expected lifecycle output, console.warn for degraded but recoverable states, console.error for failures, and reserve console.log for temporary debugging.
Use when adding or changing SQL migrations in this repo. Enforce idempotent PostgreSQL migrations, add focused migrate() regressions, and keep valid SQL unchanged even when pg-mem disagrees.
Use when pg-mem disagrees with valid PostgreSQL behavior in this repo. Patch pg-mem with patch-package, keep application SQL unchanged, add a focused regression test, and update the upstreaming docs and patch notes.