pr-sweep

Discover and manage open pull requests across repositories via GitHub CLI.

9|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/harnessprotocol/harness-kit --skill pr-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-sweep
Source: https://github.com/harnessprotocol/harness-kit/tree/main/plugins/pr-sweep/skills/pr-sweep
Command: npx skills add https://github.com/harnessprotocol/harness-kit --skill pr-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual burden of tracking, triaging, reviewing, and merging open pull requests across multiple repositories so your team can move quickly and safely.

Core Features & Use Cases

  • Cross-repo discovery & triage: Finds your open (non-draft) PRs across repos, enriches them with CI and merge state, and classifies them into actionable buckets.
  • Review and safe actions: Invokes the review skill for PRs needing review, merges what is ready, rebases behind-base PRs, and applies quick CI-fix attempts for simple failures.
  • Clear reporting: Produces an end-to-end report listing merged, rebased, fixed, and items needing human attention.

Quick Start

Install and run the skill, then ask for a sweep by saying: "Check my PRs."

Frequently Asked Questions about pr-sweep

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

FAQPage Schema
How do I automate pull request triage across multiple GitHub repositories?

Automating pull request triage across multiple GitHub repositories is done by discovering open, non-draft PRs for an author, enriching them with CI and merge state, and classifying them into actionable buckets for review or merging.

Can I automatically rebase GitHub pull requests that are behind the base branch?

Yes, you can automatically rebase GitHub pull requests that are behind the base branch. The skill identifies these PRs during cross-repo discovery and performs a rebase to bring them current with their target branch.

What is the best way to merge ready pull requests while skipping drafts?

The best way to merge ready pull requests while skipping drafts is to use an automated sweep that inspects merge-state, enforces guardrails to skip drafts, and merges classified PRs that have passing CI checks.

Does automated PR triage attempt to fix CI failures before requesting human review?

Automated PR triage does attempt to fix CI failures before requesting human review by applying quick remediation for simple failures, while still enforcing guardrails that never auto-resolve changes requested by reviewers.

Do I need the GitHub CLI to manage open pull requests across different repositories?

Yes, you need the GitHub CLI to manage open pull requests across different repositories. The skill requires access to the GitHub CLI to inspect CI checks, classify merge states, and execute operational actions like rebasing or merging.

Why does automated PR management skip pull requests with changes requested?

Automated PR management skips pull requests with changes requested to enforce safety guardrails, ensuring that human reviewers retain full control over unresolved feedback before any merging or rebasing actions are attempted.