Our review
This skill helps a team lead critically evaluate peer code review feedback by verifying each finding's existence and severity.
Strengths
- Promotes a methodical, non-dogmatic approach to feedback
- Distinguishes real bugs from architectural misunderstandings
- Prioritizes corrective actions with severity assessment
Limitations
- Requires strong project context to judge findings accurately
- May be biased if the lead over-trusts their own decisions
When a peer provides detailed code review feedback and you need to separate real issues from misinterpretations.
If you lack time or the feedback has already been validated by multiple trusted sources.
Security analysis
SafeThe skill is purely instructional text with no executable code or declared tools. It guides a user through a human-centric review process without triggering any destructive or exfiltration actions.
No concerns found
Examples
I'm a team lead. Another team lead reviewed my module and found 5 issues. Help me evaluate each finding: 1) 'The error handling in function X is insufficient' 2) 'You should use a singleton pattern for Y' 3) 'The caching layer has a race condition' 4) 'Your naming convention is inconsistent' 5) 'You forgot to close the database connection in Z'. For each, tell me if it exists, if it's valid, and what to do.A colleague claims there's a null pointer exception in our payment processing code when the amount is zero. I doubt it because we have a guard clause. Check the code and resolve the discrepancy.I received 12 findings from a code review. After evaluating them, 7 are real bugs, 3 are misunderstandings, and 2 are stylistic preferences. Prioritize the 7 real bugs by severity and suggest a fix plan.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.