pr-sweep

Monitor and categorize open pull requests across a GitHub app portfolio.

Updated May 30, 2026
One-click install
npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill pr-sweep-innerscopehearing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-sweep
Source: https://github.com/InnerScopeHearing/otchealth-claude-tools/tree/main/skills/pr-sweep
Command: npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill pr-sweep-innerscopehearing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive audit of open pull requests across your app portfolio, ensuring a clear, actionable view of their status and disposition.

Core Features & Use Cases

  • Fleet-wide PR Audit: Enumerates all open PRs and categorizes them into actionable buckets (e.g., READY-MERGE, DRAFT-GREEN, REBASE).
  • Disposition Tracking: Identifies PRs that require immediate attention or are in a non-actionable state (e.g., STALE, HOLD).
  • Machine-readable Output: Generates JSON for integration with dashboards and automation tools.
  • Gate Functionality: Can be used as a CI/CD hook to enforce PR hygiene.

Quick Start

Run the 'pr-sweep' skill to get a comprehensive PR status report for all your repositories.

Frequently Asked Questions about pr-sweep

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

FAQPage Schema
How do I track pull request status across multiple GitHub repositories?

You can track pull request status across multiple GitHub repositories by running a fleet-wide audit that enumerates open PRs and categorizes them into actionable buckets like READY-MERGE, DRAFT-GREEN, and REBASE. It uses GraphQL queries via the GitHub API to generate a comprehensive status report.

What's the best way to automate PR hygiene enforcement in a CI/CD pipeline?

To automate PR hygiene enforcement in a CI/CD pipeline, you can use this audit as a CI/CD hook to flag or label pull requests based on their status. It tracks dispositions and identifies PRs requiring immediate attention or those in a non-actionable state like STALE or HOLD.

How do I categorize stale pull requests in my GitHub app portfolio?

Categorizing stale pull requests in a GitHub app portfolio is done by auditing open PRs and sorting them into disposition buckets. The audit identifies PRs requiring immediate attention and flags those in a non-actionable state, ensuring a clear view of their status.

Does PR status tracking work with GCP Secret Manager for GitHub API authentication?

Yes, PR status tracking works with GCP Secret Manager for GitHub API authentication. The monitoring process utilizes the GitHub API for GraphQL queries and integrates directly with GCP Secret Manager to securely manage the required authentication credentials.

Can I output GitHub pull request audit results as JSON for dashboards?

Yes, you can output GitHub pull request audit results as JSON for dashboards. The monitoring process generates machine-readable JSON output, allowing you to easily integrate the categorized PR status data with existing dashboards and automation tools.