When to Use
Use this skill when reviewing code changes (diffs, PRs, or complete files) for correctness, maintainability, security, and adherence to best practices.
Steps
- Understand context: Read the full diff or file. Identify the purpose of the change (feature, bugfix, refactor, etc.).
- Check correctness: Verify logic, edge cases, error handling, and return values. Look for off-by-one errors, null/undefined handling, and race conditions.
- Assess security: Check for injection vulnerabilities (SQL, XSS, command), improper input validation, hardcoded secrets, and insecure defaults.
- Evaluate design: Consider naming clarity, function cohesion, abstraction level, and adherence to existing patterns in the codebase.
- Review tests: Check if changes are covered by tests. Identify missing test cases for edge cases and error paths.
- Rank findings: Assign severity to each finding and present them in priority order.
Severity Levels
- Critical: Bugs that will cause crashes, data loss, or security vulnerabilities in production.
- Warning: Issues that may cause problems under certain conditions or violate important conventions.
- Suggestion: Improvements to readability, naming, or style that are not strictly required.
- Nitpick: Minor style preferences with no functional impact.
Rules
- Focus on the changed code, not unrelated pre-existing issues (unless they interact with the change).
- Provide concrete fix suggestions, not just problem descriptions.
- Be specific: reference line numbers, function names, and variable names.
- Acknowledge good patterns and well-written code, not just problems.
- If you're uncertain whether something is a bug, say so and explain your reasoning.
Output Format
For each finding:
[SEVERITY] file:line — Short title
Description of the issue and why it matters.
Suggested fix or alternative approach.
End with a summary: total findings by severity, overall assessment, and whether the change is ready to merge.
Source: definableai/definable.ai — distributed by TomeVault.
1---2name: code-review-2103description: Systematic code review with severity-ranked findings Use when this capability is needed.4---56## When to Use78Use this skill when reviewing code changes (diffs, PRs, or complete files) for correctness, maintainability, security, and adherence to best practices.910## Steps11121. **Understand context**: Read the full diff or file. Identify the purpose of the change (feature, bugfix, refactor, etc.).132. **Check correctness**: Verify logic, edge cases, error handling, and return values. Look for off-by-one errors, null/undefined handling, and race conditions.143. **Assess security**: Check for injection vulnerabilities (SQL, XSS, command), improper input validation, hardcoded secrets, and insecure defaults.154. **Evaluate design**: Consider naming clarity, function cohesion, abstraction level, and adherence to existing patterns in the codebase.165. **Review tests**: Check if changes are covered by tests. Identify missing test cases for edge cases and error paths.176. **Rank findings**: Assign severity to each finding and present them in priority order.1819## Severity Levels2021- **Critical**: Bugs that will cause crashes, data loss, or security vulnerabilities in production.22- **Warning**: Issues that may cause problems under certain conditions or violate important conventions.23- **Suggestion**: Improvements to readability, naming, or style that are not strictly required.24- **Nitpick**: Minor style preferences with no functional impact.2526## Rules2728- Focus on the changed code, not unrelated pre-existing issues (unless they interact with the change).29- Provide concrete fix suggestions, not just problem descriptions.30- Be specific: reference line numbers, function names, and variable names.31- Acknowledge good patterns and well-written code, not just problems.32- If you're uncertain whether something is a bug, say so and explain your reasoning.3334## Output Format3536For each finding:37```38[SEVERITY] file:line — Short title39Description of the issue and why it matters.40Suggested fix or alternative approach.41```4243End with a summary: total findings by severity, overall assessment, and whether the change is ready to merge.4445---46> Source: [definableai/definable.ai](https://github.com/definableai/definable.ai) — distributed by [TomeVault](https://tomevault.io).47<!-- tomevault:4.0:skill_md:2026-06-16 -->