メニュー
Use when reviewing a diff, pull request, patch, or proposed implementation for bugs, regressions, missing tests, security issues, performance problems, or maintainability risks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when starting any conversation or task so the agent checks for relevant skills before acting, including before clarifying questions, exploration, implementation, review, or documentation work.
Use when the user wants a new capability, asks whether a skill exists, asks to find or install skills, or describes a recurring workflow that may already have an installable skill.
Use when choosing, adding, configuring, or reviewing MCP servers, MCP client config, tool permissions, remote server URLs, local stdio commands, or MCP-related security tradeoffs.
Use when code or config touches authentication, authorization, user input, secrets, tokens, database access, file access, external APIs, MCP servers, browser automation, dependency installation, or deployment.
Use when creating, updating, pruning, or reviewing a SKILL.md so recurring workflows become concise, reusable agent skills.
Use when implementing, fixing, refactoring, or reviewing code and you need a disciplined verification loop with builds, tests, type checks, linting, formatting, or manual checks.
| name | code-review |
| description | Use when reviewing a diff, pull request, patch, or proposed implementation for bugs, regressions, missing tests, security issues, performance problems, or maintainability risks. |
Take a reviewer stance: findings first, grounded in code references.
Review for:
Do not spend review budget on style preferences unless they hide a real defect.
Start with findings ordered by severity. For each finding include:
If there are no findings, say that directly and mention remaining test gaps or residual risk.
