safe-commit-all

Automating logical git commits requires grouping working-tree changes based on file relationships and project scope. This skill analyzes your repository to automatically stage, generate conventional commit messages, and execute commits for related modifications.

Grouping working-tree changes into conventional commits involves analyzing file relationships to create coherent units. The skill enforces the Conventional Commits specification, ensuring type(scope): description formatting for a clean project history.

Yes, you can integrate issue tracking into automated conventional commit messages. The skill automatically appends PR numbers, Sentry issue IDs, and GitHub issue references to the generated commit messages for traceability.

Yes, git CLI access is required to automate staging and committing local repository changes. The skill operates directly on local git repositories to execute staging, message generation, and commit operations.

Organizing messy git commits into coherent units requires analyzing file changes to group related code, config, and documentation updates into separate, meaningful commits. This approach enforces conventional commit standards for readable project history.

Automated conventional commit generation should be avoided if your repository does not adhere to conventional commit standards or lacks local git CLI access. The skill requires strict adherence to conventional commit specifications for all operations.