Code review
Skill wchen02/cursor-agent-learning/.cursor/skills/code-review
Review code for correctness, style, and maintainability. Use when the user asks for a code review, PR review, or feedback on changes.From its SKILL.md
npx -y skills add wchen02/cursor-agent-learning --skill code-reviewAssembled 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.1 KB, 214 tokens by cl100k_base, as published. Nobody here has run it
Code Review
When the user asks for a code review, follow this process.
Checklist
- Correctness — Logic is sound and edge cases are handled.
- Security — No obvious issues (e.g. injection, hardcoded secrets, missing validation).
- Style — Matches project conventions and is readable.
- Structure — Functions/classes are focused; duplication is minimized.
- Tests — Changes that affect behavior have or deserve tests.
Output format
Group feedback by severity:
- Critical — Must fix before merge (bugs, security).
- Suggestion — Should consider (readability, performance, patterns).
- Nice to have — Optional improvements.
Keep feedback actionable: point to files/lines and suggest concrete changes where helpful.
Scope
- If the user points to specific files or a diff, focus there.
- If they say "review my changes", use git (e.g.
git diff) to determine scope when appropriate.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.