code-reviewer
/code-reviewer
General-purpose code review skill. Provides checklists for security, code quality, performance, and best practices. Use when reviewing code changes, PRs, or performing quality audits.
- Author
- kumaran-is ↗
- Repository
- claude-code-onboarding ↗
- Licence
- MIT
- Last repository change
- 30.06.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
General-purpose code review skill. Provides checklists for security, code quality, performance, and best practices. Use when reviewing code changes, PRs, or performing quality audits.
Original author description
General-purpose code review skill. Provides checklists for security, code quality, performance, and best practices. Use when reviewing code changes, PRs, or performing quality audits.
How it works
- When to Use
- Process
- Reference Files
- Error Handling
- Anti-Patterns
- Verify
SKILL.md preview
--- name: code-reviewer description: General-purpose code review skill. Provides checklists for security, code quality, performance, and best practices. Use when reviewing code changes, PRs, or performing quality audits. allowed-tools: Read, Grep, Glob, Bash agent: code-reviewer context: fork metadata: triggers: code review, review code, PR review, pull request review, code quality, code audit, review this code related-skills: security-reviewer, dedup-code-agent, test-driven-development domain: quality role: specialist scope: review output-format: report last-reviewed: "2026-03-15" --- **Iron Law:** Never approve code without reading the actual implementation; always provide severity-bucketed findings with file:line evidence. # Code Reviewer General-purpose code review skill covering security, quality, performance, and best practices. ## When to Use - After writing or modifying code - During PR reviews - When auditing code quality ## Process 1. Identify changed files via `git diff` or user request 2. Read [reference/code-review-checklist.md](reference/code-review-checklist.md) for review categories, severity levels, and output format 3. Review each file against the checklist 4. Report findings by severity (Critical > High > Medium > Low) ## Reference Files | File | Contents | Load When | |------|----------|-----------| | `reference/code-review-checklist.md` | Security checks, code quality, performance, best practices, output format | Reviewing any code change, pre-PR checklist, security audit | ## Error Handling If no changes are found, report "No changes detected" and list the files/paths searched. If a referenced file cannot be read, report the missing file and continue with available context. ## Anti-Patterns - **Never rubber-stamp without file:line** — "looks good" with no evidence is a failed review - **Never mark APPROVED if any Critical or High finding is unresolved** — severity discipline is non-negotiable - **Never review from memory** — always read the actual changed files; filenames do not tell you what changed - **Never scope-creep the review** — report what changed, not what you wish were different in adjacent code - **Never merge findings across files** — report per-file with specific line numbers, not aggregate impressions - **Avoid vague findings** — "this could be a security issue" is not a finding; "SQL built via string concatenation at service.ts:47 allows injection" is ## Verify After completing a review: ```bash # Confirm all files you reviewed are the ones that actually changed git diff --name-only HEAD~1 # Confirm no new linting errors introduced npm run lint 2>&1 | grep -E "error|warning" | head -20 # Confirm tests still pass after changes npm test -- --passWithNoTests 2>&1 | tail -5 ``` Report format after verification: ``` REVIEW COMPLETE: - Files reviewed: N (list them) - Findings: X Critical, Y High, Z Medium, W Low - Verdict: APPROVED / NEEDS_REVIEW / REJECT - Evidence: [file:line for each finding] ```
Files in this package (2)
- SKILL.md 3 KB
- reference/code-review-checklist.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · kumaran-is/claude-code-onboarding | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| swap-cameroon/kuro-antigravity-config | 100 | MIT |
| a-pavithraa/springboot-skills-marketplace | 100 | MIT |
| borghei/Claude-Skills | 100 | MIT |
| nguyenthienthanh/aura-frog | 100 | MIT |
| yg-codes/srepowers | 100 | MIT |
| basamakcomtr/basamak-skills | 100 | MIT |
| criptogus/agent-evolve-network | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version eb5ea1893fc7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100git-pr-reviewer
Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge. - 100code-review
Comprehensive code review checklist and methodology. Use when reviewing PRs, conducting code audits, or assessing code quality. Keywords: review, PR, code review, audit, assess, quality, check - 100pr-reviewer
Review GitHub pull requests for code quality, security, and best practices. Use for automated PR feedback and approval workflows. - 100code-reviewing
Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality. - 100review
Perform a comprehensive code review on a GitHub pull request. Use when the user asks to review a PR, review code changes, check a pull request for quality, security, bugs, or best practices, or provides a PR number or GitHub PR URL to review. - 100code-review-specialist
Comprehensive code review with security, performance, and quality analysis. Use when users ask to review code, analyze code quality, evaluate pull requests, or mention code review, security analysis, or performance optimization.