code-review
Code review guidelines for commits and file changes. Covers four categories:Quality (security, correctness, maintainability), Regression (breaking changes,API compatibility), Documentation (code docs, changelogs), and Performance(optimization, efficiency).
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for automating and standardizing the code review process. By evaluating commits and file changes across four key pillars—Quality, Regression, Documentation, and Performance—it ensures that software updates are secure, maintainable, and efficient. It helps development teams maintain high code standards and prevent technical debt by providing structured feedback based on severity levels.
Use Cases
- Automated Pull Request Auditing: Use the skill to perform an initial review of PRs, flagging security vulnerabilities and maintainability issues before human review.
- Regression and API Compatibility Checks: Identify potential breaking changes in code updates to ensure seamless integration and prevent service disruptions.
- Performance Optimization: Scan new code for inefficient patterns and receive suggestions for improving execution speed and resource management.
- Documentation Compliance: Automatically verify that code changes are accompanied by necessary updates to changelogs, API specifications, and internal documentation.
- Severity-Based Issue Triage: Categorize code review findings into Critical, Warning, and Suggestion levels to help developers prioritize urgent fixes.
| name | code-review |
|---|---|
| description | | |
Categories
| Category | Reference | Focus |
|---|---|---|
| Quality | quality | Security, correctness, maintainability |
| Regression | regression | Breaking changes, API compatibility |
| Documentation | documentation | Code docs, changelogs, API specs |
| Performance | performance | Optimization, efficiency |
Severity Levels
| Level | Icon | Criteria | Action |
|---|---|---|---|
| Critical | 🔴 | Security, data loss, outage risk | Must fix |
| Warning | 🟡 | Bugs, bad practices | Should fix |
| Suggestion | 🔵 | Improvements | Consider |