git-master

To create atomic commits, this Skill analyzes your staged changes and breaks them down into multiple, focused commits based on module boundaries and logical separation, ensuring each commit represents a single, clear change.

Squashing commits during a rebase is managed by rewriting history to combine multiple commits into a single, cohesive entry, following best practices for commit granularity and dependency ordering to maintain a clean log.

Git blame and bisect enable detailed change discovery by searching commit history to pinpoint exactly when and by whom specific lines were introduced or regressed, facilitating efficient debugging and history analysis.

Yes, this Skill manages conflict resolution across various Git workflows by guiding rebase and history rewriting operations, ensuring that merge conflicts are addressed while maintaining dependency ordering and commit clarity.

You need to rewrite Git history when cleaning up a messy commit log before sharing, using rebase and squash to consolidate unrelated changes into atomic, well-described commits that improve overall code quality.

Enforcing commit granularity in version control prevents common pitfalls by ensuring changes are atomic and focused, which streamlines code review, simplifies debugging, and maintains a manageable project history.