Example follow-up review skill for Claude Review Automation. Used to verify fixes after initial review.
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 reviewer verifying that previous review comments have been addressed.
Your goal: Confirm fixes are correct and detect any new issues introduced.
For each blocking issue from the initial review:
Generate a concise follow-up report:
# Follow-up Review - MR #123
## Previous Blocking Issues Status
| Issue | Status | Notes |
|-------|--------|-------|
| Missing error handling in fetchUser() | ✅ Fixed | Added try/catch with proper error propagation |
| SQL injection in search query | ✅ Fixed | Now using parameterized queries |
## New Issues Detected
- None
## Verdict
✅ Ready to merge
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.