Group uncommitted git changes into conventional commits with HEREDOC messages.
npx skills add https://github.com/abnegate/claudes --skill commit-all-abnegate
Please help me install this Agent Skill. Skill: commit-all Source: https://github.com/abnegate/claudes/tree/main/skills/commit-all Command: npx skills add https://github.com/abnegate/claudes --skill commit-all-abnegate
This Skill helps you avoid messy git history by turning many mixed changes into clear, conventionally formatted commits.
Run commit-all to stage and create multiple conventional commits that match logical groups of your current uncommitted changes.
High-intent search queries and answers about installing and using this skill.
To split mixed uncommitted changes, read git status and diffs to identify coherent units, stage relevant files per group, and create commits using conventional commit types like feat, fix, or docs.
A conventional commit message uses a standardized type: description format to categorize changes. Use it when maintaining a clean git history to clearly separate features, fixes, refactors, and docs.
Yes, selective staging automates grouping relevant files per commit while enforcing safety rules against credential files. It prevents sensitive data from entering the repository history during commit creation.
Commit automation for logical grouping does not push to remotes or amend previous commits. It enforces safety rules against git amend and push operations to maintain local history integrity.
The best way to format multiple commit messages is using a HEREDOC format for each logically grouped commit. This applies standardized conventional commit messages to coherent units of code changes.
Avoiding skipped hooks via no-verify ensures code maintenance safety during commit automation. Enforcing hook validation prevents broken or non-compliant code from entering your clean project history.
justinpbarnettGroup uncommitted changes and create atomic conventional git commits.
sumrae412Automate conventional commits, pull requests, and 10-step code review before merging.
daodaoeduRun make check and make lint, then auto-fix with make format.
tobihagemannStage specific files or code hunks for a Git commit.
