What problem does it solve?
Maintaining existing pull requests to a merge-ready state requires manually tracking rebases, reviewer feedback, and CI failures across multiple steps, which is time-consuming and prone to oversight for development teams.
Core Features & Use Cases
- Automated PR Maintenance: Rebase PR branches on the latest base branch, resolve merge conflicts while preserving the PR's original intent, and push updated changes.
- Feedback Resolution: Address all unresolved reviewer comments with code changes, add requested tests, and reply to reviewers to confirm feedback was handled.
- CI Remediation: Identify and fix failing CI checks, distinguishing pre-existing base branch failures from issues introduced by the PR to avoid unnecessary work.
Use Case: A developer with an open feature PR that has outdated code, 3 unresolved reviewer comments, and 2 failing CI tests can use this skill to automate the entire follow-up workflow and get the PR ready for merge in minutes.
Quick Start
Use the follow-up-on-pr skill to update your existing PR #1234 by rebasing it on the main branch, addressing all open reviewer comments, fixing failing CI checks, and pushing the updated changes to the remote repository.