git-absorb

Fold staged changes into appropriate commits on a feature branch.

22|6|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/dashed/claude-marketplace --skill git-absorb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-absorb
Source: https://github.com/dashed/claude-marketplace/tree/main/plugins/git-absorb
Command: npx skills add https://github.com/dashed/claude-marketplace --skill git-absorb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates folding staged changes into the correct commits on a feature branch, helping maintain a clean and atomic Git history.

Core Features & Use Cases

  • Automatic fixup commits for reviewer feedback across multiple commits on a feature branch.
  • Autosquash-friendly workflow that avoids messy rebases.
  • Real-world use case: when reviewers request changes across several commits, this skill folds them into the proper commits automatically.

Quick Start

  • Stage the changes you want absorbed: git add <files>
  • Execute the absorb workflow: git absorb --and-rebase
  • If needed, adjust the target range with --base main and review the generated fixups: git absorb --base main --and-rebase

Frequently Asked Questions about git-absorb

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

FAQPage Schema
How do I fold staged changes into existing commits on a feature branch?

To fold staged changes into existing commits automatically, stage your files with git add, then run the absorb workflow with --and-rebase to generate and squash fixup commits into the appropriate targets.

What is the best way to handle reviewer feedback across multiple commits without a messy rebase?

Handling reviewer feedback across multiple commits is done by creating autosquash-friendly fixup commits, which automatically fold requested changes into the correct original commits to maintain a clean history.

Can I specify a base commit range when absorbing changes?

Yes, you can specify a base commit range by using the --base flag, such as --base main, to control which commits the absorb workflow targets when generating fixups for your staged changes.

How does the autosquash feature work with fixup commits?

The autosquash feature works by matching staged changes to original commits based on context, generating fixup commits, and then collapsing them into the correct targets during the rebase process for an atomic history.

Are there safety checks or recovery options when folding changes into commits?

The absorb workflow enforces prerequisites and safety checks before modifying history, providing CLI flags and documentation for recovery guidance to prevent lost changes during the fixup and rebase process.