tidy-unpushed-commits

To squash and reorder unpushed git commits safely, this skill creates an execution plan that reorganizes local history while preserving the final tree. It avoids destructive operations like hard resets and uses backup refs with diff checks to guarantee history integrity.

The best way to tidy local git history before pushing is to squash, reorder, and rewrite messages while validating that the final tree remains identical. This approach enforces non-destructive workflows and Git command discipline to guarantee history integrity.

Yes, you can rewrite commit messages on unpushed commits without losing changes. The skill preserves the final tree by using a backup ref and diff verification, ensuring that reordering or squashing does not alter your actual code modifications.

Tidying unpushed commits handles uncommitted changes by incorporating them into the safety workflow. The skill evaluates application conditions before reorganizing to ensure that existing amend or fixup instructions do not conflict with the tidying process.

You should avoid git reset --hard when reorganizing local commits because it is a destructive operation that can permanently discard work. This skill enforces non-destructive workflows with backup refs and diff checks to guarantee history integrity instead.