About code-review
A skill for reviewing a specified file or directory when code review, bug-risk checks, or pre-merge feedback are requested. It groups findings by severity and gives concrete file-level recommendations.
Key features
- 01Review a specified file or directory
- 02Identify potential bugs and risks
- 03Group findings by severity
- 04Provide file-level recommendations
Use cases
- 01Check a code change before merging
- 02Find bug risks in a specified path
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/code-reviewin Claude Code to confirm it loaded.
Details
From the project READMECode Review
Purpose
Review code for best practices and potential issues
Routing
- Use when: Use when a user explicitly asks for a code review, bug-risk sweep, or pre-merge feedback for a specific path.
- Do not use when: Don't use when the task is a broad architecture rewrite or only formatting fixes.
- Outputs: Findings grouped by severity and file-level recommendations.
- Success criteria: Returns prioritized issues with concrete fixes and no false-critical claims.
Trigger Examples
Positive
- Use the code-review skill for this request.
- Help me with code review.
- Use when a user explicitly asks for a code review, bug-risk sweep, or pre-merge feedback for a specific path.
- Code Review: provide an actionable result.
Negative
- Don't use when the task is a broad architecture rewrite or only formatting fixes.
- Do not use code-review for unrelated requests.
- This request is outside code review scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| path | string | Yes | Path to the file or folder to review |
Runtime Prompt
- Current runtime prompt length: 320 characters.
- Runtime prompt is defined directly in
../code-review.json.
Comments
Markdown supported