sweeping-prs

Automate updating, resolving conflicts, and merging open pull requests.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/souliane/teatree --skill sweeping-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sweeping-prs
Source: https://github.com/souliane/teatree/tree/main/skills/sweeping-prs
Command: npx skills add https://github.com/souliane/teatree --skill sweeping-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires workspace, ship, rules, platforms, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating, resolving conflicts, and merging open pull requests (PRs), streamlining the workflow for maintaining your repositories.

Core Features & Use Cases

  • Sequential PR Maintenance: Updates and merges PRs in a sequence to prevent conflicts and maintain branch integrity.
  • Conflict Resolution: Identifies and resolves mechanical conflicts while prompting for human intervention on semantic conflicts.
  • CI Monitoring: Watches CI pipelines to ensure PRs remain up to date.
  • Custom Merge Policies: Applies different merge policies based on repository ownership and policy configuration.
  • Use Case: Ideal for teams looking to automate the PR maintenance process without the risk of merge conflicts or manual merges.

Quick Start

Sweep your open PRs with the command: t3 <overlay> pr sweep

Frequently Asked Questions about sweeping-prs

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

FAQPage Schema
How do I automate pull request merging and resolve conflicts across multiple open PRs?

Automating pull request merging is handled by sequentially updating and merging PRs to prevent conflicts, resolving mechanical conflicts automatically while prompting for human intervention on semantic conflicts.

What is sequential PR maintenance and how does it maintain branch integrity?

Sequential PR maintenance updates and merges open pull requests one by one in a sequence, ensuring branch integrity by reducing the risk of conflicts that arise from concurrent manual merges.

Do I need a workspace setup and CI integration to automate PR maintenance?

Yes, automating PR maintenance requires workspace setup and CI integration to monitor pipelines, apply custom merge policies, and ensure pull requests remain up to date before merging.

Can I apply custom merge policies based on repository ownership?

Yes, custom merge policies can be applied based on repository ownership and policy configuration, allowing teams to enforce different rules for various repositories during PR automation.

How does CI pipeline monitoring work for open pull requests?

CI pipeline monitoring watches continuous integration pipelines to ensure open pull requests remain up to date, preventing merges that would break build integrity or introduce untested code.

When should I prompt for human intervention during PR conflict resolution?

Human intervention during PR conflict resolution is required for semantic conflicts, while mechanical conflicts are identified and resolved automatically by the merge automation process.