git-master

To create atomic commits in git, you stage related changes alongside their tests and group modifications by responsibility, ensuring each commit implements a single intent. This Skill automates that splitting process by planning commit groups before execution.

The best way to achieve clean git history is applying structured rebasing and squashing operations with safety checks for rewriting history. This Skill encodes commit strategies that reorder and squash commits to produce understandable, demarcated history.

Git bisect works effectively with atomic commits because each commit represents a single focused intent, making it easier to identify which change introduced a bug. This Skill enforces those well-scoped commits to improve traceability and blame operations.

To prepare a feature branch for code review, you ensure test files accompany implementations and write concise, language-consistent commit messages following detected style. This Skill guides staging related changes and grouping them by responsibility for review readiness.

You should avoid rewriting git history with rebasing or squashing when safety checks indicate potential conflicts or when commits are not properly planned and justified. This Skill enforces structured commit strategies with safety checks to prevent problematic history rewrites.