Commit Skill

To keep git history clean, stage only files related to a single logical change and commit using conventional-commits messages. This enforces one logically scoped commit per change to improve history clarity and traceability across all workspace repositories.

Conventional commits style standardizes commit messages to ensure consistent git history. It provides a structured format for features, bug fixes, refactors, docs, and configuration updates, making changes easier to trace and understand.

Split bulk code changes by using a chunking workflow. Stage only the files related to a single logical change, run pre-commit checks, adjust author and date controls, and commit with a scoped message before moving to the next chunk.

Yes, the one-commit rule applies across all repositories in your workspace. It handles various change types including features, bug fixes, refactors, docs, and configuration updates to guarantee consistent messages and clean history.

The best way to enforce traceability is to apply the one-commit rule. By ensuring every commit represents a single logical change with consistent conventional-commit messages, you prevent bulk updates and maintain a clean, traceable git history.

Pre-commit checks guarantee consistent messages and clean history. They validate that your staged changes represent a single logical change before the commit is finalized, preventing bulk updates from polluting your git history.