pr-janitor

Classify pull request progress and triage blockers into healthy, action_required, or blocked states.

4|1|Updated Feb 3, 2026

Search Tags:#automation #pr #triage #ci #pull-request #blocker #bounded-fixes

Ready to run

npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-janitor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-janitor
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/pr-janitor
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-janitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PRs in flight often stall due to failing checks, conflicts, or ambiguous review blockers. This skill watches progress, identifies blockers, and suggests bounded interventions to keep PRs moving without overreaching.

Core Features & Use Cases

Monitor PR progress and gate checks and review states to detect blockers early.
Classify blockers as healthy, action_required, or blocked and propose bounded remediation when safe.
Produce a truthful, structured progress artifact for handoffs to code-review or finish stages.

Quick Start

Resolve a concrete PR target (pr_number, pr_url, or branch) and let the skill begin monitoring CI, conflicts, and review state to report a truthful progress result.

Frequently Asked Questions about pr-janitor

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

FAQPage Schema

How do I triage pull request blockers like CI failures and merge conflicts?▼

To triage pull request blockers, you classify PR progress and identify CI failures, merge conflicts, or review blockers, then apply bounded remediation to keep PRs moving safely without overreaching.

What is the best way to monitor draft PR progress and gate checks?▼

Monitoring draft PR progress involves watching gate checks and review states to detect blockers early, classifying them as healthy, action_required, or blocked, and suggesting bounded interventions when safe.

How do I automate PR triage for in-flight branches under review?▼

Automating PR triage for in-flight branches requires resolving a concrete PR target like pr_number, pr_url, or branch, then monitoring CI, conflicts, and review state to report a truthful progress result.

Does this PR triage approach produce structured output for code review handoffs?▼

Yes, PR triage produces a truthful, structured progress artifact designed specifically for handoffs to code-review or finish stages, satisfying bounded remediation policy and PR metadata inspection requirements.

When should I not use automated bounded fixes for open PRs?▼

You should avoid automated bounded fixes when blockers are classified as blocked rather than action_required, as the skill only proposes bounded remediation when safe to keep PRs moving without overreaching.

Can I monitor open PRs without specifying a pull request number?▼

Yes, you can monitor open PRs by resolving a concrete PR target using pr_number, pr_url, or branch name, allowing the skill to begin monitoring CI, conflicts, and review state flexibly.