git-master

To split complex multi-file changes into atomic git commits, this Skill analyzes your working tree and generates a structured commit plan that maps changes to specific features or fixes. It enforces a multi-phase workflow to ensure each commit remains a focused, reviewable unit.

The safest way to rebase and squash commits on a feature branch is using a structured workflow with built-in guardrails. This Skill executes history editing through analysis, planning, and verification phases to prevent accidental data loss and maintain history hygiene.

To enforce test pairing when planning git commits, this Skill integrates test validation into its commit execution phase. It ensures every planned atomic commit is checked against corresponding tests before history is finalized, aligning outcomes with project conventions.

You can force-push rebased history safely because this Skill provides built-in guardrails for force-push operations and collaboration. It enforces strict verification phases during history edits to prevent accidental data loss on shared feature branches.

Yes, this git workflow automation handles complex multi-file version control changes by enforcing an atomic commit planning process. It analyzes the changes, generates a reproducible commit plan, and validates the execution to maintain a trustworthy history.

You should avoid using automated git rebasing strategies on branches where collaboration guardrails cannot be enforced or when commit verification fails. The Skill's multi-phase workflow is designed for feature branches to ensure history hygiene without risking data loss.