reviving-stale-prs

Rebase stale GitHub pull requests and run quality gate checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill reviving-stale-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviving-stale-prs
Source: https://github.com/christian-byrne/ticket-to-pr-pipeline/tree/main/skills/reviving-stale-prs
Command: npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill reviving-stale-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of evaluating and reviving stale GitHub Pull Requests, saving developers time by identifying and addressing outdated code changes.

Core Features & Use Cases

  • Automated Triage: Assesses PRs for viability by checking for superseding work, code compatibility, and author engagement.
  • Conflict Resolution: Rebases stale PRs onto the latest main branch and resolves merge conflicts.
  • Quality Gate Enforcement: Runs automated quality checks to ensure the PR meets project standards.
  • Use Case: When a PR has been open for months, this Skill can determine if it's still relevant, rebase it, fix any issues, and prepare it for merging, or close it if it's no longer needed.

Quick Start

Use the reviving-stale-prs skill to revive pull request number 123 in the repository owner/repo.

Frequently Asked Questions about reviving-stale-prs

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

FAQPage Schema
How do I automatically rebase a stale GitHub pull request onto the main branch?

To rebase a stale GitHub pull request, this Skill automates triage by checking for superseding work, rebasing the PR onto the latest main branch, and resolving merge conflicts automatically. It evaluates author engagement to ensure the PR is still viable before attempting the rebase.

What is the best way to triage old pull requests for code compatibility and relevance?

Triage old pull requests by assessing them for code compatibility, superseding work, and author engagement. This Skill handles automated triage by evaluating these viability factors for stale GitHub PRs, determining if the code changes are still relevant before proceeding with conflict resolution.

Do I need GitHub CLI and git worktree to resolve conflicts on outdated pull requests?

Yes, you need GitHub CLI and git worktree utilities to resolve conflicts on outdated pull requests. These dependencies are required for execution, enabling the Skill to perform automated triage, rebase stale PRs, handle merge conflict resolution, and run local quality gates.

When should I close a stale PR instead of reviving it?

You should close a stale PR instead of reviving it when the automated triage identifies superseding work, determines code incompatibility, or finds no author engagement. This Skill prepares viable PRs for merging or closes them if they are no longer needed.

Can I automate conflict resolution for GitHub pull requests that have been open for months?

You can automate conflict resolution for PRs open for months by using this Skill to rebase stale pull requests onto the latest main branch and resolve merge conflicts. It checks for superseding work and code compatibility before preparing the PR for merging.