triage-community-work

Groups open non-maintainer PRs/issues by urgency and severity into a structured triage report.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ourchitecture/idp --skill triage-community-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-community-work
Source: https://github.com/ourchitecture/idp/tree/main/.agents/skills/triage-community-work
Command: npx skills add https://github.com/ourchitecture/idp --skill triage-community-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintainers quickly identify community-submitted PRs and issues that require attention, ensuring external contributors are acknowledged and guided.

Core Features & Use Cases

  • Triage and categorize open community contributions by urgency and maintainer availability.
  • Generate a structured triage report including contributor, age, waiting-on, reasons, severity, and next steps.
  • Automatically surface recommended actions to keep external contributors engaged and projects moving forward.

Quick Start

Review open community PRs and issues and assign timely maintainer actions.

Frequently Asked Questions about triage-community-work

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

FAQPage Schema
How do I triage community pull requests and issues on GitHub faster?

Triage community pull requests and issues by automatically identifying non-maintainer contributions, grouping them by urgency, and outputting a structured report with severity and recommended next steps.

What is the best way to categorize open GitHub issues by waiting-on status and maintainer availability?

Categorize open GitHub issues by applying automated triage logic that groups items based on waiting-on status, contributor type, and urgency to help maintainers prioritize actions.

How do I generate a structured triage report for external GitHub contributors?

Generate a structured triage report by scanning all open community-submitted items, capturing reasons for delay, and surfacing recommended actions to keep external contributors engaged.

Can I automatically surface recommended actions for community-submitted PRs needing attention?

Yes, automatically surface recommended actions by identifying community-contributor items needing attention, evaluating their age and severity, and assigning timely maintainer actions.

Does this automated triage process work with all open PRs and issues authored by non-maintainers?

Yes, automated triage applies to all open PRs and issues authored by non-maintainers, ensuring external contributors are acknowledged and guided through structured next steps.

When do I need to use automated GitHub issue triage for open source projects?

Use automated GitHub issue triage when you need to quickly identify community-submitted PRs and issues that require maintainer attention, ensuring external contributors are acknowledged and guided.