Quickly triages a contributor pull request or reported issue against repository policy and lightweight evidence without full review or root-cause analysis. Publishes the disposition to GitHub, and on a contributor pull request that links no issue it may open a tracking issue and close the pull request. Use when the user asks to "triage this contributor PR", "sanity-check this PR", "triage this issue", "reproduce this reported issue", "check whether this bug still exists", or invokes /prp-maintainer-triage.
72
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The canonical home for this skill is prp-maintainer-triage in Wirasm/prp
Resolve one GitHub pull request or issue, then load only its lightweight triage workflow.
Input: $ARGUMENTS (if absent, use the target named in the conversation).
Determine the target type from GitHub metadata, not keyword guesses. For a bare number, resolve a pull request with that number first, then an issue. If no single target can be resolved, ask the user which PR or issue to triage.
references/pr-triage.md completely, then execute it end to end with the original input. Do not read the issue workflow.references/issue-triage.md completely, then execute it end to end with the original input. Do not read the PR workflow.Do not triage both kinds in one invocation or route into a heavier workflow.
references/pr-triage.md — lightweight contributor PR policy and reviewability triagereferences/issue-triage.md — lightweight issue reproduction and disposition4352925
Canonical home
since Oct 6, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.