afc:triage

Automate parallel triage of GitHub pull requests and issues into a prioritized report.

7|Updated Feb 19, 2026

Search Tags:#code review #github #prioritization #pull requests #issues #triage

Ready to run

npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: afc:triage
Source: https://github.com/jhlee0409/all-for-claudecode/tree/main/skills/triage
Command: npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of managing open pull requests and issues by automating their collection, parallel analysis, and prioritization.

Core Features & Use Cases

Parallel Triage: Analyzes multiple PRs and issues concurrently to identify risks, complexity, and required actions.
Selective Deep Analysis: Performs lightweight analysis first, then optionally checks out PR branches for build/test verification.
Coupling Detection: Identifies file-level dependencies between PRs to flag potential merge conflicts.
Use Case: When faced with a backlog of 50 open PRs and 30 issues, use this Skill to get a prioritized report highlighting critical items, ready-to-merge PRs, and potential blockers, saving significant developer time.

Quick Start

Use the afc:triage skill to triage all open pull requests and issues in the current repository.

Frequently Asked Questions about afc:triage

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

FAQPage Schema

How do I prioritize a large backlog of open GitHub pull requests and issues?▼

You can automate parallel triage of open GitHub pull requests and issues to generate a prioritized report highlighting risks, complexity, and required actions for critical items and blockers.

Can I detect potential merge conflicts between open pull requests?▼

Yes, you can detect potential merge conflicts between open pull requests by identifying file-level dependencies and cross-PR file coupling, which flags overlapping changes that might cause conflicts during merging.

How do I verify build and test status for pending pull requests?▼

You can verify build and test status for pending pull requests by using selective deep analysis with worktree isolation, which checks out PR branches to run build and test verifications safely.

Do I need the gh command line tool to triage GitHub issues?▼

Yes, you need the gh command line tool installed to triage GitHub issues, as the automated collection and analysis of open pull requests and issues depends on it for repository access.

What is the best way to identify ready-to-merge pull requests in a repository?▼

The best way to identify ready-to-merge pull requests is to run an automated parallel analysis that evaluates PR risk, complexity, and cross-PR file coupling to isolate safe merges from blockers.

Can I run lightweight code review analysis before deep testing?▼

Yes, you can run lightweight code review analysis before deep testing, as the triage process performs initial parallel checks and optionally follows with deep worktree isolation for builds.