commit-discipline

To enforce clean commit messages, run the commit-discipline skill before committing to ensure each commit is focused on a single concern and follows clear message guidelines. This maintains a readable audit trail.

The best way to maintain a single concern per commit is to use a pre-commit check that validates your changes. This skill provides rules ensuring one change per commit to promote a maintainable codebase.

Clear git commit messages require specific prefixing conventions and message structure. This skill provides guidelines for writing informative commit messages that maintain code quality and ensure a clear audit trail.

Yes, you can use commit rules to improve code quality before pushing. The skill offers a pre-commit message check to run before committing code, ensuring your commits adhere to single-concern rules.

Your git commit history lacks readability when commits mix multiple changes. Enforcing one change per commit and using clear commit message guidelines resolves this by maintaining a clean codebase.

Yes, commit-discipline works without external dependencies. It functions as a standalone skill in your development environment to enforce commit rules and maintain code quality.