follow-up-on-pr

Automate rebasing, reviewer feedback, and CI fixes for pull requests.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/ElbertePlinio/dotfiles --skill follow-up-on-pr-elberteplinio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: follow-up-on-pr
Source: https://github.com/ElbertePlinio/dotfiles/tree/main/private_dot_factory/plugins/marketplaces/factory-plugins/plugins/code-review/skills/follow-up-on-pr
Command: npx skills add https://github.com/ElbertePlinio/dotfiles --skill follow-up-on-pr-elberteplinio

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about follow-up-on-pr

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

FAQPage Schema
How do I automate pull request follow-ups to get them merge-ready?

Automating pull request follow-ups involves rebasing branches on updated base branches, resolving reviewer comments, and fixing failing CI checks. This eliminates manual maintenance by coordinating synchronization, code updates, local validation, and remote pushes to achieve a merge-ready state.

What does automated PR maintenance include when resolving reviewer feedback?

Automated PR maintenance addresses unresolved reviewer comments by implementing code changes, adding requested tests, and replying to reviewers. It ensures feedback resolution is tracked and handled while preserving the PR's original intent throughout the workflow.

Can I use an automated workflow to fix failing CI checks across any programming language?

Yes, automated CI remediation works across any programming language or project type. It identifies failing CI checks and distinguishes pre-existing base branch failures from issues introduced by the PR to avoid unnecessary work and ensure merge readiness.

How do I rebase an existing PR branch on the latest base branch without losing the original intent?

Rebasing an existing PR branch requires synchronizing with the updated base branch and resolving merge conflicts while preserving the PR's original intent. Automated workflows handle this branch synchronization and push the updated changes to the remote repository.

Does automated PR follow-up work with existing GitHub pull requests that have outdated code and failing tests?

Yes, it applies to all active GitHub pull requests requiring maintenance. It handles outdated code, unresolved reviewer comments, and failing CI tests by coordinating branch synchronization, code changes, validation runs, and reviewer communication.