pr-gardening

Discover, verify, and drive instance-authored GitHub pull requests to merge-ready state.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill pr-gardening-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-gardening
Source: https://github.com/nabitllc/todero/tree/main/.agents/skills/pr-gardening
Command: npx skills add https://github.com/nabitllc/todero --skill pr-gardening-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Open pull requests authored by an automated Todero instance drift out of date, accumulate failing checks, and lose track of their originating issues. This Skill mechanically discovers those PRs, verifies readiness at the current head SHA, and drives non-ready ones back to green without ever merging, approving, or closing anything. ## Core Features & Use Cases - Scoped Candidate Discovery: Scans Todero issues via the extract-search API for PR URLs, deduplicates them, and filters by author allowlist so community contributions are excluded by default. - Current-Head Readiness Verification: Re-fetches each PR's head SHA and evaluates check runs, Greptile results, review decisions, merge conflicts, and base-branch distance to assign ready, needs_gardening, or report_only verdicts. - Automated Remediation Loop: Dispatches /prepare-todero-pr tasks for non-ready PRs with cooldowns, round limits, and task deduplication, then publishes a confidence-bucketed Markdown report. - Use Case: A Todero operator runs the workflow weekly to find all open PRs the instance authored in the last 14 days, identify which have failing CI or missing Greptile reviews, and automatically dispatch fix tasks while generating an auditable report. ## Quick Start Ask the agent to run pr-gardening in dry-run mode to discover and report on all open pull requests this Todero instance authored 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 check if my open pull requests are merge-ready?

Run the check-readiness script, which re-fetches each PR's current head SHA and evaluates status checks, Greptile check-runs, review decisions, merge conflicts, and commits behind the base branch. It assigns ready, needs_gardening, or report_only verdicts with machine-readable reasons.

How do I automatically fix failing checks on GitHub pull requests?

The workflow dispatches a /prepare-todero-pr task per non-ready PR with the exact failing reasons from readiness verification. It enforces a 48-hour cooldown and a maximum of three gardening rounds before recommending human disposition.

Does this workflow merge or approve pull requests automatically?

No. The skill has hard guardrails: it never merges, approves, or closes pull requests, and never instructs others to do so. All GitHub access is read-only, limited to gh pr view and GET API requests.

Can I include community-authored pull requests in the gardening scope?

By default only PRs authored by the gh-authenticated login are in scope; community PRs are dropped into droppedCommunityPullRequests. You can widen scope explicitly with --authors for specific logins or --include-community to disable the filter.

What happens when a pull request is a draft?

Draft pull requests are treated as report-only. The workflow records their readiness reasons but never posts gardening comments or dispatches prepare tasks for them.

Why does the readiness check report greptile_missing?

The verdict requires a completed Greptile check-run on the exact current head SHA with a success or neutral conclusion. If no Greptile run exists at that head, the PR is marked needs_gardening until one completes.