code-review
How to review code; a pull request, feature branch, local changes etc.
56
65%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/code-review/SKILL.mdWhen asked to review code, whether a PR on GitHub or some local changes, provide feedback on:
- Code quality and best practices
- Potential bugs or issues
- Performance considerations
- Security concerns
- Test coverage
Use the repository's CLAUDE.md for guidance on style and conventions.
For comments, changelog entries, and PR bodies, review against the standard in
.claude/skills/prose-pass/SKILL.md — read it as
criteria; do not invoke it, since it edits files and a review may have nothing
checked out.
If you encounter terms that should be added to the glossary, invoke the glossary
skill using: Skill tool with skill="glossary"
Be constructive and helpful in your feedback.
- Repository
- Consensys-Incorporated/ocap-kernel
- Commit
3d5aea9
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.