Our review
Critically evaluates peer review findings by verifying each issue in the code, distinguishing valid from invalid, and producing a prioritized action plan.
Strengths
- Prevents blind adoption of review comments
- Checks each finding against the actual code
- Categorizes findings as valid or invalid with clear reasoning
- Prioritizes actions based on confirmed severity
Limitations
- Requires codebase access and project context
- Ambiguous findings may need further investigation
- Does not fix issues, only identifies those worth fixing
Use when you receive code review feedback from another source and need to decide which items to act on.
Not needed when the review is fully trusted and you intend to implement every suggestion directly.
Security analysis
SafeThe skill is a meta-instruction for evaluating peer review findings; it doesn't involve code execution or system modifications.
No concerns found
Examples
Here is the peer review feedback: [PASTE FINDINGS]. Before adding anything to the backlog, verify each finding against the codebase. For each, tell me if it's real or not, and why. Then give me a prioritized list of actions.I'm the tech lead. Another AI model reviewed my PR and reported these issues: [FINDINGS]. Check the code carefully and tell me which issues are legitimate. For false positives, explain what the reviewer misunderstood.Act as a skeptical team lead. Evaluate these findings from a peer review: [FINDINGS]. Confirm which are actual bugs, rate their severity, and propose a fix order.A different team lead within the company has reviewed the current code/implementation and provided findings below. Important context:
- They have less context than you on this project's history and decisions
- You are the team lead - don't accept findings at face value
- Your job is to critically evaluate each finding
Findings from peer review:
[PASTE FEEDBACK FROM OTHER MODEL]
For EACH finding above:
- Verify it exists - Actually check the code. Does this issue/bug really exist?
- If it doesn't exist - Explain clearly why (maybe it's already handled, or they misunderstood the architecture)
- If it does exist - Assess severity and add to your fix plan
After analysis, provide:
- Summary of valid findings (confirmed issues)
- Summary of invalid findings (with explanations)
- Prioritized action plan for confirmed issues
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.