Automated summary
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
How this analysis is madeExamples
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/critical-evaluation-of-peer-review-ms8gxndp/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/critical-evaluation-of-peer-review-ms8gxndp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/critical-evaluation-of-peer-review-ms8gxndp/download' --output '.skill-downloads/critical-evaluation-of-peer-review-ms8gxndp/SKILL.md.part' && mv '.skill-downloads/critical-evaluation-of-peer-review-ms8gxndp/SKILL.md.part' '.skill-downloads/critical-evaluation-of-peer-review-ms8gxndp/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/critical-evaluation-of-peer-review-ms8gxndp/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.