takeover-pr

Evaluate stale pull requests for takeover eligibility and prepare successor changes.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill takeover-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: takeover-pr
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/takeover-pr
Command: npx skills add https://github.com/gittower/git-flow-next --skill takeover-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you take over a pull request when review feedback has gone unanswered long enough to justify a successor PR, while preserving the original contributor’s work and credit.

Core Features & Use Cases

  • Eligibility Verification: Checks the latest maintainer review, elapsed time, and post-review author activity before taking any action.
  • Worktree-Based Preservation: Creates a separate worktree, reuses the contributor’s commits, and applies requested changes on top.
  • Review-Driven Follow-Up: Builds a review plan from existing comments, runs validation, prepares a successor PR, and drafts a courteous closing comment.
  • Use Case: A maintainer needs to replace a stale PR after the response window has expired, but wants to keep the contributor’s authorship intact and communicate the transition clearly.

Quick Start

Ask to evaluate PR 42 for takeover eligibility and, if eligible, prepare the successor changes and draft the public PR and closing comments.

Frequently Asked Questions about takeover-pr

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

FAQPage Schema
How do I take over a stale pull request on GitHub while preserving the original author's commits?

To take over a stale pull request, you can evaluate the PR's review activity and create a worktree to apply changes on top of the contributor's commits. This preserves authorship while preparing a successor PR.

When is a GitHub pull request considered stale enough for a maintainer to take over?

A GitHub pull request is considered stale enough for takeover when a maintainer review has gone unanswered past an acceptable response window and the original author shows no post-review activity. The Skill verifies these conditions before proceeding.

How do I apply requested code review changes to an abandoned branch without losing the contributor's credit?

You apply requested code review changes by creating a separate worktree, reusing the original contributor's commits as a base, and adding your modifications on top. This process maintains the contributor's authorship intact in the git history.

Can I automatically generate a closing comment for a superseded pull request?

Yes, you can automatically generate a drafted courteous closing comment for a superseded pull request. The Skill drafts public messaging that clearly communicates the transition while giving credit to the original author.

Does taking over a branch require running build and test validation?

Yes, taking over a branch requires running build and test validation. The Skill builds a review plan from existing comments, applies the requested changes, and validates the build before preparing the successor PR.

What is the best way to replace an inactive PR with a successor PR?

The best way to replace an inactive PR is to generate a review plan from existing comments, apply changes via a worktree, validate the build, and draft a successor PR with a courteous closing message. This ensures a smooth transition.