findings-pass

Verifies and rules a run's findings independently, presenting outcomes in one ranked table.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill findings-pass-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: findings-pass
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/findings-pass
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill findings-pass-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? After a work session or code review, leftover findings pile up with no clear verdict — some may be duplicates, some already tracked, some false alarms. This Skill rules every finding cold: each claim is re-verified by an independent checker, deduplicated, searched against the issue tracker, and assigned exactly one outcome, all shown in a single table where every row states whether it was verified. ## Core Features & Use Cases - Independent verification: Each candidate finding is re-measured by a verifier that never saw the finder's reasoning, so unproven or refuted claims are caught before they become tracker noise. - Deduplication and mechanism grouping: Findings reported multiple times collapse into one candidate, and confirmed findings sharing a root cause are grouped into a single row rated by their most severe instance. - Tracker-aware ruling: Every confirmed row is searched against the issue tracker and ruled as INTO an existing issue, DROP, a new record proposal, or HAND OVER as a unit of work — with no writes happening without the user's explicit word. - Use Case: A session finishes a feature branch with eight unresolved reviewer comments. Run the pass to verify each against the current base, drop the two already tracked as issue #42, group three sharing one cause, and present a ranked table of proposals for the user to approve. ## Quick Start Ask the assistant to run a cold findings pass over the findings left standing from this session and show the verified results in one table.

Frequently Asked Questions about findings-pass

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage code review findings before filing issues?▼

Run a findings pass that re-verifies each candidate independently, deduplicates repeats, groups findings sharing one cause, and searches the tracker for existing issues. Each row then gets exactly one outcome — into an existing issue, dropped, a new record, or handed over as work.

How to verify findings from another session or reviewer?▼

Hand the findings text over and the pass treats each as a claim, stripping the finder's reasoning. An independent verifier re-reads the code at the named coordinate on the refreshed base, so stale or unproven claims are caught before ruling.

Does the findings pass write to the issue tracker automatically?▼

No, the pass is report-only and edits no code. Tracker writes go through the issue-tracking skill only after the user explicitly approves specific rows; without that answer, proposals stay undecided rather than being filed or dropped.

What happens when a finding cannot be verified?▼

Unverifiable findings are marked not measured — unreachable where no readable tree carries the coordinate, budget where checks outrun capacity, or failed where the verifier never answered. They are never ruled as refuted and carry over to a later pass.

When should I not use a findings pass?▼

Do not use it to review a change — that is the multi-review skill's job — or inside a wave batch, whose candidates ride its return to the master session. Critical findings on code the run itself wrote go back to the fix path instead of being ruled.