evaluate-findings
Critically assess external feedback (code reviews, AI reviewers, PR comments) and decide which suggestions to apply using adversarial verification. Use when the user asks to \"evaluate findings\", \"assess review comments\", \"triage review feedback\", \"evaluate review output\", or \"filter false positives\".
npx skills add majiayu000/claude-skill-registry --skill evaluate-findings --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Evaluate Findings Assess external feedback (code reviews, AI suggestions, PR comments) with adversarial verification. Triage findings into actionable verdicts. Do not apply fixes. ## Step 1: Assess Each Finding For each finding: 1. **Read the referenced code** at the mentioned location — include the full function or logical block, not just the flagged line 2. **Check for early exits:** - If the finding references code that no longer exists or has since changed, skip it and note that the code has diverged. - If two findings conflict with each other, skip both and document the conflict. 3. **Determine scope** — clarify whether the issue was introduced by the PR/changeset or is pre-existing. Present this distinction explicitly so the user can decide whether it belongs in this PR's scope. - Pre-existing issues in earlier commits on the same feature branch are in-scope by default — the entire branch is one coherent unit of work. - Out-of-scope findings that are genuinely useful and have low blast radius should be accepted. Only skip out-of-scope findings when the change is disproportionate to the current work. 4. **Verify the claim** against the actual code — does the issue genuinely
- Step 1: Assess Each Finding
- Step 2: Devil's Advocate
- Subagent Verdicts
- Step 3: Reconciliation
- Step 4: Format Output
What does the evaluate-findings skill do?
Critically assess external feedback (code reviews, AI reviewers, PR comments) and decide which suggestions to apply using adversarial verification. Use when the user asks to \"evaluate findings\", \"assess review comments\", \"triage review feedback\", \"evaluate review output\", or \"filter false positives\".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill evaluate-findings --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.