メニュー
Review changed code for reuse, quality, and efficiency, then fix any issues found.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Identify changed code and dispatch reuse, quality, and efficiency reviewer agents in parallel; return the raw findings list.
Review changed code for reuse, quality, and efficiency, and produce a triaged list of findings (no edits). Use after writing code, for simpler code with fewer bugs and better performance.
Provides guidance on good software design principles, with trade-off calibration, examples, and common failure modes. Applies when making decisions while writing, designing, or refactoring code, or evaluating trivial code for clarity, maintainability, and common mistakes.
Reviews code with a team against established software design principles, and returns triaged findings (no edits). Use when evaluating code, or after writing or refactoring complex code, systems or technical designs: for code that is clearer, easier to maintain, and avoids common mistakes.
Shared setup for shaping sessions. Determines if an artefact exists or needs creating, creates it if needed, starts the transcript, reads the type taxonomy. Called by the parent router or by any sub-skill invoked directly.
Shape an artefact through structured Q&A. Routes to the right sub-skill: brainstorm (new/unclear artefacts), refine (open decisions), or discover (exploration-driven artefacts like People and Ideas).
| name | code-review:fix |
| description | Review changed code for reuse, quality, and efficiency, then fix any issues found. |
Run a code review and fix the issues found.
Read and follow code-review/investigate/SKILL.md to get the raw findings list. Dispatch reviewers as parallel subagents; do not inline.
Aggregate the findings and decide which are worth applying. Briefly summarise the result for the user — what's worth applying and anything notable being skipped, with the reasoning.
Apply each finding marked worth applying. Skipped findings are not fixed — do not argue with the triage. When done, briefly summarise what was fixed and what was skipped, with the reasoning. If the code was already clean, say so in one line and skip the fix.
