skills.rest
Wirasm
WirasmCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prp-maintainer-triage

Triages GitHub pull requests and issues against repository policy with lightweight evidence checks.

2.2k|608|Updated Jun 21, 2025
Search Tags:#open source#triage#gitHub#maintainer#Issue#Code review#Pull request
One-click install
npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-maintainer-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prp-maintainer-triage
Source: https://github.com/Wirasm/PRPs-agentic-eng/tree/main/plugins/prp-core/skills/prp-maintainer-triage
Command: npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-maintainer-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maintainers spend significant time deciding whether incoming pull requests and reported issues deserve attention. This Skill performs a fast, policy-driven triage of a single GitHub PR or issue, producing a clear verdict without the cost of a full code review or root-cause analysis.

Core Features & Use Cases

  • PR Triage: Checks contributor PRs against intake rules, repository direction, focus, and check status, then returns a READY, CONTRIBUTOR_ACTION, CLOSE, or MAINTAINER_DECISION verdict.
  • Issue Triage: Reproduces reported symptoms cheaply on the current development head and dispositions issues as CONFIRMED, DUPLICATE, FIXED_CURRENT, REPORTER_ACTION, POLICY_CLOSE, or MAINTAINER_DECISION.
  • Safe Publication: Supports a --no-publish dry-run mode, uses only existing labels, keeps comments idempotent, and treats contributor content as untrusted.
  • Use Case: A maintainer facing a backlog of 30 open PRs runs the triage on each one to quickly label which are ready for review, which need contributor fixes, and which should be closed.

Quick Start

Ask the assistant to triage GitHub issue or pull request number 123 in this repository using the maintainer triage workflow.

Frequently Asked Questions about prp-maintainer-triage

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

FAQPage Schema
How do I triage a GitHub pull request quickly?▼

Provide the PR number or URL and the workflow checks intake rules, repository direction, PR focus, and check status without a full code review. It returns a READY, CONTRIBUTOR_ACTION, CLOSE, or MAINTAINER_DECISION verdict with evidence.

How to check whether a reported GitHub issue still exists?▼

The issue triage workflow reproduces the reported symptom on the latest supported development head using the cheapest faithful method. It then dispositions the issue as CONFIRMED, FIXED_CURRENT, DUPLICATE, or REPORTER_ACTION based on the observed result.

Can I run the triage without changing anything on GitHub?▼

Yes, pass the --no-publish flag to receive the verdict, decisive evidence, and proposed comments, labels, and state changes without mutating GitHub. This lets you review the disposition before any public action.

Does the triage workflow perform a full code review or root-cause analysis?▼

No, it deliberately stops at lightweight policy checks and symptom reproduction. It does not diagnose causes, plan fixes, run full test suites, or execute contributor code, keeping the investigation cheaper than a full review.

What happens when triage evidence is conflicting or policy is unclear?▼

The workflow returns a MAINTAINER_DECISION verdict stating the exact unresolved decision. It does not comment or close in that case, and only applies an existing needs-maintainer label when that matches repository practice.

Related Skills

Explore More Software Engineering Skills→
warpdotdevwarpdotdev
292

dedupe-issue

Compare GitHub issue titles and descriptions to flag potential duplicates.

Official
Intermediate
synthesisengineeringsynthesisengineering
15

synthesis-pr-review

Analyzes pull request diffs for regressions, risk, and integration readiness.

Official
Intermediate
FerroxLabsFerroxLabs
21

ferrox-inbox

Triages GitHub issues and pull requests against project templates and contribution rules.

Community
Advanced
chapzinchapzin
1

Bug Investigation

Identify and resolve bugs through structured root cause analysis with reproducible steps and verification gates.

Community
Intermediate