stale-branch-fix

Rebase stale PR branches onto main and restore CI checks.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill stale-branch-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stale-branch-fix
Source: https://github.com/PLeVasseur/opencode-project-agents/tree/main/safety-critical-rust-coding-guidelines/skills/stale-branch-fix
Command: npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill stale-branch-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rebase stale PR branches to the latest main, repair CI failures, and push fixes back to the PR branch to restore green checks automatically.

Core Features & Use Cases

  • Identify stale PRs and failed CI checks from PR URLs and generate a remediation plan.
  • Rebase branches onto main, resolve conflicts, and ensure CI can pass locally before pushing.
  • Create or update plan notes in the repo and push updates to the PR head to trigger CI re-run.

Quick Start

Run stale-branch-fix on the target PR URLs to automatically rebase and restore CI.

Frequently Asked Questions about stale-branch-fix

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

FAQPage Schema
How do I rebase stale git branches onto the latest main branch?

To rebase stale git branches, this process collects pull request URLs, rebases the branch onto the latest main, resolves conflicts, and pushes updates to the PR head to trigger CI re-runs.

How do I restore green CI checks on failing pull requests automatically?

Restoring green CI checks involves collecting failing check metadata for each PR URL, creating a remediation plan, resolving conflicts locally, and pushing updates to verify CI passes successfully.

Can I use automation to fix multiple stale PR branches at once?

Yes, you can use automation to fix multiple stale PR branches by providing target PR URLs, which generates a remediation plan to rebase branches and resolve conflicts before pushing updates.

What's the best way to resolve conflicts when rebasing a stale pull request?

The best way to resolve conflicts when rebasing a stale pull request is to use an automated remediation plan that rebases onto the latest main, resolves conflicts, and ensures CI passes locally.

Why does my CI pipeline keep failing after I rebase a stale branch?

CI pipelines keep failing after a rebase if conflicts are not properly resolved or local checks are bypassed; the skill ensures CI passes locally before pushing updates to the PR head.