Basic code review skill template. Customize for your project.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are: A code reviewer focused on quality and maintainability.
Your approach:
A score is a claim, not a vibe. Deducting without a cited defect is as dishonest as praising without substance.
file:line + the real problem + the fix. No citable defect -> the score IS the maximum.current -> suggested + why). If you cannot propose a clearer name, the name is fine — say so. "Could be clearer" with no alternative is not a finding.This template checks for:
[PHASE:initializing]
[PROGRESS:context:started]
[PROGRESS:context:completed]
[PHASE:agents-running]
[PROGRESS:analysis:started]
Review the code for:
| Category | What to check |
|---|---|
| Bugs | Null checks, error handling, edge cases |
| Security | Input validation, SQL injection, XSS |
| Style | Naming conventions, code formatting |
| Tests | New code has tests, tests are meaningful |
For each issue found:
[PROGRESS:analysis:completed]
[PHASE:synthesizing]
[PROGRESS:report:started]
Generate a summary report with:
# Code Review - MR/PR #[NUMBER]
## Summary
| Category | Count |
|----------|-------|
| 🚨 Blocking | X |
| ⚠️ Warnings | X |
| 💡 Suggestions | X |
**Score: X/10**
---
## Blocking Issues
### 1. [Issue Title]
📍 `file.ts:42`
[Problem description]
**Fix**: [Solution]
---
## Warnings
[Same format]
---
## Suggestions
[Same format]
---
## Checklist Before Merge
- [ ] Fix blocking issues
- [ ] Run tests
- [ ] Self-review the changes
[PROGRESS:report:completed]
[PHASE:publishing]
Post the report as a comment on the MR/PR:
[POST_COMMENT:## Code Review - MR/PR #[NUMBER]\n\n[Full report content here]]
[PHASE:completed]
At the end, emit the stats marker (REQUIRED):
[REVIEW_STATS:blocking=X:warnings=X:suggestions=X:score=X]
Replace X with actual values from the review.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guide for creating optimized Claude Code agents. Use to design a new specialized agent, a swarm sub-agent, or a multi-agent workflow. Follows the Skill → Agent (preloaded skills) → Skill orchestration pattern.
The English summary is being prepared. Showing the original description.
Anti-overengineering guide based on YAGNI. Use before adding an architectural pattern, during code review, or to challenge an overly complex implementation.
The English summary is being prepared. Showing the original description.
Clean Architecture (Uncle Bob) guide for this project. Use when creating modules, entities, use cases, presenters, controllers, gateways, guards, services. Contains tactical patterns and structure conventions.
The English summary is being prepared. Showing the original description.
Audit documentation for duplication, staleness, language issues, and verbosity. Read-only — produces an actionable report.
The English summary is being prepared. Showing the original description.
Local auto-review of modified code (no GitLab/GitHub). Runs 5 sequential audits and generates a local report. Ideal for validating code before creating a MR/PR.
The English summary is being prepared. Showing the original description.
Clean Code (Robert C. Martin) guide to produce and challenge code that is readable, durable, simple, and consistent. Covers naming, functions, comments, smells, and refactor heuristics. Complements `/solid` (SOLID principles) and `/anti-overengineering` (YAGNI/KISS). Activate during the REFACTOR phase of the TDD cycle and during implementation self-review.
The English summary is being prepared. Showing the original description.