review-triage

Name: review-triage
Availability: InStock
Author: psaab

Automate triage and verification of code review findings against a live git master branch.

8|2|Updated Feb 8, 2026

Search Tags:#automation #security #github #audit #triage #code-review

Ready to run

npx skills add https://github.com/psaab/xpf --skill review-triage-psaab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-triage
Source: https://github.com/psaab/xpf/tree/main/.claude/skills/review-triage
Command: npx skills add https://github.com/psaab/xpf --skill review-triage-psaab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent, unverified, and poorly documented code review triage by enforcing a rigorous, evidence-based verification process for every finding.

Core Features & Use Cases

Evidence-Based Triage: Validates findings against the current master branch using a three-gate verification process (existence, fix status, and material impact).
Automated Issue Tracking: Automatically files genuine, novel findings as individual GitHub issues with full provenance.
Audit Trail Generation: Produces a detailed result file for every review, ensuring every disposition is justified with specific code references and severity reasoning.

Quick Start

Run the review-triage skill to process all pending review files in the temporary directory and generate the corresponding GitHub issues and audit reports.

Frequently Asked Questions about review-triage

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

FAQPage Schema

How do I automate code review triage against a live git repository?▼

Automating code review triage involves validating findings against the current master branch using a three-gate verification process. This ensures every disposition is justified with specific code references and severity reasoning before tracking bugs.

What is evidence-based triage for security audits?▼

Evidence-based triage for security audits verifies code review findings through existence, fix status, and material impact checks. This method enforces a rigorous verification process for every finding against the live repository source code.

Do I need GitHub CLI and local source code access to automate issue tracking?▼

Yes, automating issue tracking requires git, GitHub CLI, and local access to the target repository source code. These dependencies allow the system to verify findings against the master branch and file genuine novel findings as GitHub issues.

How are code review findings documented for high-integrity audits?▼

Code review findings for high-integrity audits are documented by producing a detailed audit trail result file. This ensures every disposition is justified with specific code references and severity reasoning for every processed review.

What is the best way to verify existing bug fixes in a master branch?▼

The best way to verify existing bug fixes is applying a three-gate verification process checking for existence, fix status, and material impact. This validates findings against the current master branch to ensure accurate triage.