conventional-commits

To organize uncommitted git changes into atomic conventional commits, this skill analyzes your working tree and maps code modifications to specific build steps. It groups changes by architectural layers to construct a disciplined, step-by-step project history.

The best way to split fast-forwarded fixes into reviewable commits is using a correction protocol support mechanism. This skill safely divides mixed file modifications into distinct, logical build-step commits ordered by dependency sequence.

Reconstructing a messy working tree into a step-by-step project history requires mapping exploratory changes to a strict build-sequence architecture. This skill aligns uncommitted work into atomic commits following the Hedgehog loop sequence.

Yes, you need a git-based version-control workflow to apply the Hedgehog commit vocabulary. This skill requires adherence to the Hedgehog classification system for scope and type to properly order commits by build-sequence dependency.

You need to group code changes by build steps like schema, contract, or service layers when reconstructing history after exploratory changes. This ensures each commit represents exactly one logical build step in your architectural sequence.