Table of Contents generated with DocToc
Maintainer-facing PR-queue management for projects with a public contributor PR queue. Three skills that compose into a complete triage + review pass:
APPROVE / REQUEST_CHANGES / COMMENT review with inline comments, posts on confirmation.Why a framework skill family? These skills were originally maintained inside apache/airflow as breeze pr auto-triage and breeze pr stats — useful for any ASF project with a meaningful contributor-PR queue, but locked behind airflow-specific toolchain. Lifting them into the framework lets other adopters reuse the playbook with their own adopter-config files for project-specific knobs (committers team handle, area-label prefix, comment-template wording, CI-check → doc-URL map, review-criteria source files).
| Skill | Purpose |
|---|---|
pr-management-triage | First-pass triage. Successor to breeze pr auto-triage. |
pr-management-stats | Read-only summary tables grouped by area label. |
pr-management-code-review | Deep code review, one PR at a time. |
The skills resolve project-specific content from these files in the adopter's <project-config>/ directory:
| File | Used by |
|---|---|
pr-management-config.md | pr-management-triage, pr-management-stats |
pr-management-triage-comment-templates.md | pr-management-triage |
pr-management-triage-ci-check-map.md | pr-management-triage |
pr-management-code-review-criteria.md | pr-management-code-review |
The framework currently ships with airflow-flavoured defaults inline in the supporting files of each skill (e.g. pr-management-triage/comment-templates.md embeds airflow's PR-quality-criteria URL). A follow-up PR will complete the extraction so the skills read exclusively from <project-config>/. Until then, non-airflow adopters override by forking the relevant supporting file into their own .claude/skills/<skill-name>/.
projects/_template/README.md — adopter scaffold index, including the four PR-management config files.