follow-up-on-pr

Rebase pull requests, resolve reviewer feedback, and fix CI failures.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/oElberte/dotfiles --skill follow-up-on-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: follow-up-on-pr
Source: https://github.com/oElberte/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/oElberte/dotfiles --skill follow-up-on-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you take over an existing pull request and turn it into a merge-ready change by updating it to the latest base branch, addressing review feedback, and resolving any CI regressions that block merging.

Core Features & Use Cases

  • PR takeover and update: Rebases the PR branch onto the latest base branch so it stays compatible and avoids merge conflicts.
  • Reviewer-feedback resolution: Reviews the fetched inline and general comments, implements requested changes, and replies to resolved threads.
  • CI-focused stabilization: Runs local lint/format/test/typecheck checks, distinguishes pre-existing failures from PR-introduced ones, and updates code accordingly.

Example use case: you’re given a PR URL where reviewers requested changes and CI is failing; you use this skill to rebase, implement the missing fixes, get tests passing, push updates, and leave a clear review response.

Quick Start

Follow up on PR #9996 by rebasing it onto the latest base branch, applying reviewer-requested changes, running the relevant local checks, and force-pushing the updated branch.

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 rebase a pull request onto the latest base branch and resolve merge conflicts?▼

You can rebase a pull request by providing a PR URL or number to fetch current metadata, rebasing the branch onto the latest base branch, resolving conflicts, and force-pushing the updated branch.

What is the best way to address code review feedback and reply to reviewer threads on GitHub?▼

Addressing code review feedback involves fetching inline comments, implementing requested changes, committing fixes with clear messages, and replying to resolved threads to mark feedback as addressed.

How do I fix failing CI checks and distinguish pre-existing failures from PR-introduced errors?▼

Fixing CI failures requires running scoped local lint, format, test, and typecheck checks based on repository tooling, then separating pre-existing failures from PR-introduced errors before updating the code.

Can I take over an existing pull request and make it merge-ready using a single workflow?▼

Yes, you can take over an existing pull request by studying diffs, rebasing on the base branch, implementing missing fixes, passing local checks, and pushing updates to make the PR merge-ready.

Does this PR follow-up workflow require specific git tools or dependencies to run?▼

No specific git tools or dependencies are required; the workflow uses your existing repository tooling to run scoped local checks and relies on standard git commands for rebasing and force-pushing.

When should I update a pull request description during the rebase and review process?▼

You should update the pull request description when the scope changes during the feedback resolution process, ensuring the PR accurately reflects the implemented fixes and current merge readiness state.