Classify GitHub issues and pull requests into actionable work items.
npx skills add https://github.com/yash-garg/pi-config --skill triage-yash-garg
Please help me install this Agent Skill. Skill: triage Source: https://github.com/yash-garg/pi-config/tree/main/skills/triage Command: npx skills add https://github.com/yash-garg/pi-config --skill triage-yash-garg
This Skill helps maintainers turn unstructured GitHub issues and pull requests into organized, actionable work items by applying a consistent triage process.
Use the triage skill to review open issues needing attention and prepare the selected issue for the next workflow stage.
High-intent search queries and answers about installing and using this skill.
Triage workflows classify GitHub issues as bugs or enhancements and move them through structured states to produce actionable work items. This involves evaluating requests, verifying claims, and preparing structured handoffs with clear acceptance criteria.
Preparing pull requests for agent handoffs means generating durable briefs with acceptance criteria, scope boundaries, and implementation guidance. This ensures coding agents receive structured, actionable instructions rather than unstructured repository maintenance requests.
Issue classification for repository maintenance categorizes incoming GitHub requests as bugs or enhancements and applies structured state transitions. This triage process evaluates each issue consistently and moves it through defined stages before generating acceptance criteria.
You can track out-of-scope decisions and rejected requests during issue triage. Maintaining out-of-scope knowledge and identifying previously rejected requests avoids repeated evaluation and helps maintainers focus on valid issue tracking practices.
No external dependencies are required to automate pull request triage workflows. The triage process operates independently to classify requests, generate acceptance criteria, and prepare agent briefs without needing additional integration components or external libraries.
Avoid automating issue evaluation when a request lacks sufficient context for classification or when scope boundaries remain unclear after initial verification. Complex repository maintenance scenarios requiring nuanced human judgment may also exceed automated triage state transitions.
photon-groveSummarize open pull requests, issues, and stuck items in a GitHub repository.
semicolon-devteamAssign GitHub Issues to Sprints in GitHub Projects with capacity checks.
workinprogress-aiSynchronize roadmap Markdown files with GitHub issue and pull request states.
FabienDehopreCategorize and verify GitHub issues and pull requests into triage states.
