Code review
The playbook library. Teach your agents what the docs won't
npx -y skills add NinetrixAI/skills-hub --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.
What its author says it does
Copied from the file, not written here
Systematic code review playbook
SKILL.md
1.0 KB, as published. Nobody here has run it
Code Review
When reviewing code, follow this process:
- Read the diff — understand what changed and why
- Check correctness — look for logic errors, edge cases, off-by-one bugs
- Check security — SQL injection, XSS, command injection, secrets in code
- Check style — consistent naming, no dead code, clear variable names
- Check tests — are new code paths covered? Are edge cases tested?
Severity levels
- Critical: Security vulnerabilities, data loss risks, crashes
- Major: Logic errors, missing error handling, performance issues
- Minor: Style issues, naming, documentation gaps
Rules
- Always explain why something is a problem, not just what
- Suggest a concrete fix for every issue found
- Acknowledge good patterns — don't only report negatives
- Never approve code with Critical issues