skills.rest
erclx
erclxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-followup

Stage, commit, and push follow-up edits to an open pull request branch.

2|Updated Jan 13, 2026
Search Tags:#automation#git#workflow#code review#pull request#github
One-click install
npx skills add https://github.com/erclx/aitk --skill git-followup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-followup
Source: https://github.com/erclx/aitk/tree/main/claude/skills/git-followup
Command: npx skills add https://github.com/erclx/aitk --skill git-followup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of managing post-PR edits, ensuring that follow-up commits are properly staged, pushed, and synced with the existing pull request without creating messy, disconnected review threads.

Core Features & Use Cases

  • Automated PR Syncing: Automatically updates the PR body and title when a follow-up commit changes the scope of the work.
  • Review Comment Management: Posts a summary of the fix as a PR comment when review feedback is addressed, while avoiding duplicate replies.
  • Use Case: After a reviewer requests a small change on an open PR, use this skill to stage the fix, commit it, push to the branch, and notify the reviewer in one command.

Quick Start

Use the git-followup skill to ship the current changes as a follow-up to the open pull request.

Frequently Asked Questions about git-followup

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

FAQPage Schema
How do I push follow-up commits to an open pull request branch?▼

To push follow-up commits to a pull request, you need an upstream branch and an open PR. This automates staging, committing, and pushing self-review edits while syncing PR metadata and posting summary comments to existing review threads.

Can I automatically update PR title and body when addressing code review feedback?▼

Yes, you can automatically update the PR title and body when a follow-up commit changes the scope of the work. This ensures the pull request metadata stays synced with the latest pushed changes.

What is the best way to notify reviewers after fixing GitHub pull request comments?▼

The best way to notify reviewers after fixing GitHub pull request comments is to post a summary of the fix as a PR comment. This avoids duplicate replies and maintains seamless review threads.

Do I need an open pull request to automate Git workflow follow-up commits?▼

Yes, you need an open pull request and an upstream branch to execute the follow-up commit workflow. The automation relies on syncing with existing PR metadata and active review threads.

How to avoid duplicate replies when addressing code review feedback on GitHub?▼

To avoid duplicate replies when addressing code review feedback, the automation posts a single summary comment of the fix to the existing PR review thread. This prevents messy, disconnected review threads.

Related Skills

Explore More Software Engineering Skills→
nodatallnodatall
2

cleanup-merged-branches

Delete merged Git branches locally and remotely with safety checks.

Community
Intermediate
jimmymalhanjimmymalhan
1

rebase-manager

Rebase dependent pull request branches onto main after a base PR merges.

Community
Intermediate
joseph-c-mcguirejoseph-c-mcguire
1

06-tech-tooling

Set up and validate linters, formatters, and test runners for CI builds.

Community
Advanced
dtsongdtsong
1

GitHub PR Respond

Fetch and respond to GitHub pull request review comments.

Community
Intermediate