메뉴
Delegate a code review task to Claude Code via the claude_code MCP tool. Use when you want Claude's judgment on architecture, security, correctness, test coverage, or code quality for files you've just written or modified.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Full audit→fix→verify cycle: Claude audits, Codex fixes, Claude verifies. Repeats up to 3 rounds until all issues are resolved or the user stops. Claude does all code reading and judgment; Codex does all file editing.
Diagnose the cc-suite setup in the current project. Runs the full health check, explains every issue, and fixes what can be fixed automatically. Skill counterpart to /cc-suite:diagnose.
Initialize cc-suite for the current project — sets up the AGENTS.md bridge, registers Codex and Claude MCP servers, and generates a .cc-suite.md config. Skill counterpart to /cc-suite:init.
Non-interactive re-run of all cc-suite bridge and registration scripts. No questions asked — idempotent escalation step after the diagnose skill finds issues it could not fix. Skill counterpart to /cc-suite:repair.
Use when writing, reviewing, or naming any cc-suite artifact — pick the canonical noun or verb from this registry rather than coining a synonym. Loaded by NLPM's scorer and checker when R51 is enabled in .claude/nlpm.local.md.
Use when creating, editing, or reviewing a cc-suite advisor agent (a value-over-rules persona under `.cc-suite/agents/`). Covers system-prompt phrasing, model choice, tool restrictions, working-dir scoping, budget/turn limits, and the file format. Use proactively whenever the user asks to "add an agent", "make an advisor", "write a reviewer", or edits anything under `.cc-suite/agents/`.
| name | claude-review |
| description | Delegate a code review task to Claude Code via the claude_code MCP tool. Use when you want Claude's judgment on architecture, security, correctness, test coverage, or code quality for files you've just written or modified. |
| version | 0.2.0 |
Delegate a code review to Claude Code and get back structured findings.
Call claude_code with a structured review prompt:
mcp__claude-code__claude_code:
prompt: |
Review the following code for correctness, security, and quality.
SCOPE: {files or description of what to review}
Evaluate:
1. Correctness — logic errors, edge cases, off-by-one, race conditions
2. Security — injection, auth bypass, data exposure, input validation
3. Quality — readability, maintainability, test coverage, naming
4. Architecture — coupling, abstraction leaks, layer violations
For each finding report:
- File:line
- Severity: Critical / High / Medium / Low
- Category
- Issue description
- Suggested fix
PROVENANCE NOTE: The code being reviewed was written by OpenAI Codex. Evaluate
with full rigor — do not defer to it. Apply independent judgment on every finding.
cwd: {project working directory}
effort: high
permissionMode: plan
Save the returned session_id as {review_session_id}.
To ask about specific findings or request deeper analysis on a section:
mcp__claude-code__claude_code_reply:
session_id: {review_session_id}
prompt: "Expand on finding #3 — what's the exact attack vector and what's the minimal fix?"
Display the review findings in a structured table:
| File:Line | Severity | Category | Issue | Fix |
|---|---|---|---|---|
| ... | Critical | Security | ... | ... |
Follow with a summary count by severity and a recommended action (fix now vs fix later vs acceptable risk).
permissionMode: plan prevents Claude from modifying files — review is read-onlyeffort: high for thorough analysis; use medium for quick spot-checkscwd to anchor relative file paths in findingsclaude-debug — use when findings point to a specific bug that needs root-cause tracingclaude-implement — use after review to have Claude apply the suggested fixes autonomously$audit-fix — use when review reveals a recurring pattern that needs a systematic fix cycle