Review code
Structured code review checklist for quality, security, and correctness. Triggers: review code, code review, review changes, review implementationFrom its SKILL.md
npx -y skills add samelie/claude-plugin-pnpm --skill review-codeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, as published. Nobody here has run it
/review-code
Perform a structured code review on recently changed files.
Review Checklist
1. Correctness
- Does the code do what the requirements/design specify?
- Are edge cases handled?
- Are error paths handled correctly?
- Do types match the data flow?
2. Security
- Input validation at system boundaries?
- No injection vectors (SQL, XSS, command)?
- No hardcoded secrets or credentials?
- Auth/authz checks in place where needed?
3. Patterns & Conventions
- Does the code match existing codebase patterns?
- Are naming conventions followed?
- Is the code organized like similar modules?
- Are imports organized consistently?
4. Maintainability
- Is the code readable without excessive comments?
- Are abstractions appropriate (not premature, not missing)?
- Is coupling between modules reasonable?
- Would a new developer understand this code?
5. Performance
- Any obvious O(n²) or worse in hot paths?
- Unnecessary allocations or copies?
- Missing early returns or short-circuits?
Steps
- Identify changed files — from coder progress reports or
git diff - Read each file — understand the full context, not just the diff
- Apply checklist — evaluate each section systematically
- Classify findings:
- Critical — must fix before merge (bugs, security, data loss)
- Warning — should fix (patterns, maintainability)
- Suggestion — nice to have (style, minor improvements)
- Write review — structured output with file, line, category, description, fix
Rules
- Be specific — cite files and line numbers
- Don't manufacture issues — if code is good, say so
- Focus on what matters, not style nitpicks
- One finding per issue, not one finding per file