absorb-review-fixes

Fold review-feedback fixes into owning branch commits via fixup and autosquash rebase.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Hallmanac/hall9k --skill absorb-review-fixes-hallmanac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: absorb-review-fixes
Source: https://github.com/Hallmanac/hall9k/tree/main/.claude/skills/absorb-review-fixes
Command: npx skills add https://github.com/Hallmanac/hall9k --skill absorb-review-fixes-hallmanac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often lands as messy "address feedback" commits that clutter a PR's history. This Skill folds each fix into the branch commit that owns it, so the PR reads as clean, authored narrative history instead of a patchwork of review reactions. ## Core Features & Use Cases - Mechanical Commit Mapping: Assigns each fix to the most recent branch commit touching the same file, splitting fixes across owners when needed. - Fixup + Autosquash Workflow: Uses git commit --fixup and git rebase -i --autosquash to rewrite history without manual interactive editing. - Tree-Identity Verification: Enforces both git diff and git status --porcelain checks to prove the rebased tree matches the tested tree and no fix was left uncommitted. - Use Case: During a Hall9k follow-up run, review comments arrive on a PR using the narrative commit style; the Skill absorbs each fix into its owning commit and leaves the branch ready for the daemon's force-with-lease push. ## Quick Start Ask the agent to absorb the current working-tree review fixes into their owning branch commits using the absorb-review-fixes workflow.

Frequently Asked Questions about absorb-review-fixes

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

FAQPage Schema
How do I fold review fixes into existing commits with git?

Stage each fix, run git commit --fixup=<owning-commit> for the commit that owns the touched files, then run GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash origin/<base>. Verify with git diff and git status that the tree is unchanged before pushing.

How do I decide which commit a review fix belongs to?

A fix belongs to the most recent branch commit that touches the same file, found with git log -1 --format=%h origin/<base>..HEAD -- <file>. Fixes spanning files owned by different commits split into one fixup per owning commit.

Why is git diff empty but a review fix was still lost after rebase?

An empty diff between the old tip and HEAD cannot detect a fix that was never staged or committed, since it exists in neither tree. Run git status --porcelain as a second check to catch uncommitted fixes before pushing.

When should I not use fixup and autosquash for review feedback?

Do not use this approach when the project uses the append commit style, where fixes are simply committed on top. It also does not apply to genuinely new scope, which should become a new properly-titled commit instead.

How do I safely push a rebased PR branch?

Push with git push --force-with-lease, never plain --force, so the push fails if the branch moved on origin. In a Hall9k follow-up run, do not push manually; the daemon pushes with force-with-lease after re-verifying.