squash-unit

Consolidate intermediate commits into a single final commit using squash-unit.

24|2|Updated Nov 6, 2025

Search Tags:#git #workflow #commits #squash #version-control #inception #unit

Ready to run

npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill squash-unit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: squash-unit
Source: https://github.com/ikeisuke/ai-dlc-starter-kit/tree/main/skills/squash-unit
Command: npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill squash-unit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates multiple intermediate commits produced during Unit completion or Inception Phase into a single, coherent final commit, helping keep the project history readable.

Core Features & Use Cases

Unit completion squash: combine the commits since the Unit start into one final commit.
Inception Phase squash: squash commits that occur during Inception Phase into a single consistent entry.
Retroactive squashing: optionally squash past Unit commits using explicit start and end points as needed.

Quick Start

Run the squash-unit skill with the target cycle and unit to perform a dry-run and then complete the squash with a generated commit message.

Frequently Asked Questions about squash-unit

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

FAQPage Schema

How do I squash intermediate git commits from a unit completion into one clean history?▼

You can squash intermediate commits from Unit completion into a single final commit by running the squash-unit skill, which consolidates the git history since the unit start into one clean entry.

Can I preview a git commit squash before applying it to my branch?▼

Yes, squash-unit supports dry-run previews, allowing you to review the consolidated commit message and history changes before actually applying the squash to your cycle branch.

How do I retroactively squash past commits in a version control workflow?▼

You can retroactively squash past commits by providing explicit start and end points, allowing the squash-unit skill to consolidate previous unit commits into a single coherent entry.

What is a baseline commit and do I need one to squash git history?▼

A baseline commit anchors the squash operation by serving as the starting reference point. You need a baseline commit to determine where the unit start is and to execute the commit consolidation correctly.

Does squash-unit work with inception phase commits or only unit completion branches?▼

Squash-unit works with both. It consolidates Inception Phase commits into a single consistent entry and also combines commits from Unit completion into one final commit on cycle branches with unit numbers.

What's the best way to consolidate multiple git commits during a development cycle?▼

The best way is to use a dedicated squash skill that detects cycle branches, identifies the unit start, generates a commit message file, and consolidates all intermediate commits into a single readable history entry.