ワンクリックで
code-review-and-quality
Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | code-review-and-quality |
| description | Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact. |
Use this skill when reviewing a diff written by yourself, another agent or a human, or when deciding whether a change is ready to merge.
Identify correctness risks, test gaps, maintainability problems, hidden regressions and security concerns before the change lands.
tdd-practice — tests as review evidencelogical-fallacy-review — invalid reasoning in review commentsgit-workflow-and-versioning — reviewable atomic changesguardrails-safety-patterns — security findings in reviewUse when reviewing plans, recommendations, prioritisation, risk registers, retrospectives or agent outputs for judgement distortion from cognitive bias — not for checking whether an argument's premises validly support its conclusion.
Use when evaluating whether premises in plans, ADRs, reviews, security justifications or agent recommendations validly support their conclusions — for logical fallacies, not judgement distortion from cognitive bias.
Use when a coding agent needs robust problem solving, explicit decomposition, alternative-path exploration, program-aided reasoning, ReAct loops, or self-correction.
Use when generated code, plans, tests, prompts or architecture need critique, repair and verification before completion; especially for coding tasks requiring self-review, test-driven repair or quality gates.
Identifies risks, scores likelihood and impact, selects treatment, assigns owners and review cadence. Use when building or updating a risk register, treating agent autonomy risks, or deciding mitigate, transfer, accept or avoid.
Identifies assets, trust boundaries, threats and mitigations for systems and agents. Use when designing security-sensitive features, reviewing attack surface, or planning abuse-case tests.