git-committer

To enforce atomic git commits, you need a validation mechanism that disallows multiple unrelated changes in a single commit. This skill automatically validates staged changes to ensure each commit represents a single, cohesive modification.

Limiting git commit message length for Korean text requires setting a strict character maximum. This skill enforces a 50-character limit specifically for Korean noun-ending messages to keep your git logs concise and highly readable.

Yes, you can block workflow artifacts like plan.md and docs/specs/ from being committed in git. This skill prohibits committing these generated files and requires proper staging discipline to keep your repository clean.

Setting up pre-commit rules for test and build success gates involves applying frontmatter-driven validation rules to your workflow. This skill automatically enforces these gate requirements, preventing commits if tests or builds fail.

Yes, this git commit discipline skill works without external dependencies. It operates independently using built-in references and frontmatter-driven rules to validate commit messages, atomic changes, and test gates directly within your development workflow.

Using atomic commits instead of grouping multiple changes in git ensures that each commit represents a single logical modification. This discipline prevents non-atomic changes, simplifies code reviews, and makes tracking or reverting specific updates significantly easier.