skills.rest
mkusaka
mkusakaCOMMUNITY
Explore all skills by this author →
GitHub

code-review-phase-2-verify-3-state

Verify code review findings with a verifier tool and voting definitions.

7|Updated Mar 8, 2026
Search Tags:#quality assurance#code review#verification#software quality#findings classification
One-click install
npx skills add https://github.com/mkusaka/ccskills --skill code-review-phase-2-verify-3-state
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-phase-2-verify-3-state
Source: https://github.com/mkusaka/ccskills/tree/main/skills/code-review-phase-2-verify-3-state
Command: npx skills add https://github.com/mkusaka/ccskills --skill code-review-phase-2-verify-3-state

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the precision-tier verification of code review findings, ensuring each finding is correctly categorized.

Core Features & Use Cases

  • Deduplication: Identifies and removes duplicate candidates that refer to the same issue.
  • Verification: Uses a verifier tool to vote on each candidate's accuracy (CONFIRMED, PLAUSIBLE, REFUTED).
  • Filtering: Retains candidates with a CONFIRMED or PLAUSIBLE vote for further action.

Quick Start

Run the verification process on the code review findings with the command: verify-findings

Frequently Asked Questions about code-review-phase-2-verify-3-state

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

FAQPage Schema
How do I verify code review findings for accurate classification?▼

Code review findings verification automates candidate classification using a voting mechanism to categorize each finding as CONFIRMED, PLAUSIBLE, or REFUTED, ensuring consistent quality assurance.

How do I remove duplicate code review findings before verification?▼

Deduplication identifies and removes duplicate candidates that refer to the same issue before the verification process begins, ensuring each code review finding is unique.

What is the best way to filter confirmed code review findings for further action?▼

Filtering code review findings retains only candidates with a CONFIRMED or PLAUSIBLE vote, discarding refuted entries to ensure only verified software quality issues proceed to further action.

How does the voting mechanism work for code review verification?▼

The voting mechanism uses a verifier tool to assess each code review candidate's accuracy, assigning a classification of CONFIRMED, PLAUSIBLE, or REFUTED to ensure precise findings verification.

Can I apply precision verification to existing code review workflows?▼

Precision verification is applicable to code review workflows that require accurate classification of findings, integrating into existing quality assurance processes without additional dependencies.

Related Skills

Explore More Software Engineering Skills→
Netflix-SkunkworksNetflix-Skunkworks
76

railguard-securityagentsonly-scan

Run all 12 security subagents unconditionally to collect raw vulnerability findings for benchmarking.

Official
Advanced
apacheapache
79

magpie-issue-fix-workflow

Draft code fixes with automated tests for confirmed issue tracker items.

Official
Intermediate
CyapstayeCyapstaye
9

requesting-code-review

Scan staged diffs for security vulnerabilities and logic errors before commit.

Community
Advanced
silva2kandsilva2kand

multi-pr-review

Automate pull request reviews with multiple AI agents and consensus prioritization.

Community
Advanced