Our review
Critically evaluates peer code review findings by verifying their existence and severity before taking action.
Strengths
- Promotes critical thinking about external feedback
- Reduces unnecessary changes by rejecting false positives
- Delivers a prioritized action plan for confirmed issues
Limitations
- Requires deep familiarity with the codebase
- May be biased by ownership of the code
- Not a substitute for a structured review process
When receiving a detailed peer review from someone with less context, to validate each finding before implementing changes.
For trivial or self-evident feedback, or when the reviewer is fully trusted without need for verification.
Security analysis
SafeThis skill provides a template for evaluating peer review feedback, with no executable instructions, code, or tool usage. It poses no risk of destructive actions or data exfiltration.
No concerns found
Examples
A team lead has reviewed our implementation and provided these findings: [PASTE FINDINGS]. I'm the lead for this project. Analyze each finding: verify if the issue exists, assess severity, and provide a summary of valid and invalid findings plus a prioritized action plan.Here are suggestions from another team: [LIST]. For each, check the code and tell me if they're real issues or misunderstandings. Then give me a fix plan for real ones, and explain why the others don't apply.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.