pr-gardening

Automate the maintenance and readiness verification of pull requests opened by Paperclip agents.

79.8k|14.6k|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/paperclipai/paperclip --skill pr-gardening
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-gardening
Source: https://github.com/paperclipai/paperclip/tree/main/.agents/skills/pr-gardening
Command: npx skills add https://github.com/paperclipai/paperclip --skill pr-gardening

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the operational overhead of managing multiple AI-generated pull requests, ensuring they remain merge-ready without requiring manual intervention or constant human oversight.

Core Features & Use Cases

  • Automated Readiness Checks: Validates PR status, mergeability, Greptile check-runs, and CI status against the current head SHA.
  • Proactive Maintenance: Automatically triggers /prepare-paperclip-pr for PRs that are not yet ready, driving them toward a mergeable state.
  • Use Case: A team managing dozens of agent-authored PRs can use this Skill to identify stale or failing branches, automatically re-run preparation tasks, and generate a consolidated report of PR health.

Quick Start

Run the pr-gardening skill to discover and verify the readiness of all pull requests opened by this instance in the last 14 days.

Frequently Asked Questions about pr-gardening

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

FAQPage Schema
How do I monitor PR readiness with this skill?

Run the skill to execute the discovery and verification stages, which check CI status, merge conflicts, and Greptile results. The output provides a readiness verdict for each PR, categorizing them as ready, needing gardening, or report-only.

Does this skill automatically merge my pull requests?

No, this skill strictly adheres to a read-only policy regarding PR lifecycle management. It never merges, approves, or closes pull requests, ensuring that all final decisions remain with human developers.

Can I use this skill for community contributions?

By default, the skill filters out community contributions to focus on agent-authored PRs. You can override this behavior using the --include-community flag, though it is recommended to keep the default scope for safety.

Why are some of my PRs marked as stale?

PRs are marked as stale if they have no activity within the configured window, which defaults to 14 days. This prevents the gardener from wasting resources on abandoned or inactive branches.