From commit-commands
Amends the most recent commit with additional file changes or an updated message. Verifies the commit hasn't been pushed and preserves the original commit type unless instructed otherwise.
How this command is triggered — by the user, by Claude, or both
Slash command
/commit-commands:amendThe summary Claude sees in its command listing — used to decide when to auto-load this command
Amend the most recent commit with additional changes or an updated message. ## Steps 1. Verify the last commit has not been pushed to remote: 2. If there are additional file changes to include: 3. Decide whether to update the commit message: 4. Verify the amended commit looks correct: 5. If the original commit was already pushed: ## Format ## Rules - Never amend a commit that has been pushed without explicit user approval. - Always verify no unintended changes are included in the amendment. - Preserve the original commit type (feat, fix, etc.) unless instructed otherwise.
Amend the most recent commit with additional changes or an updated message.
Amended Commit: <hash>
Message: <commit message>
Files Changed: <list>
Force Push Required: <yes|no>
5plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub smarks26/awesome-claude-code-toolkit --plugin commit-commands/amendAmends the most recent commit with additional file changes or an updated message. Verifies the commit hasn't been pushed and preserves the original commit type unless instructed otherwise.
/amendAmends the last commit with staged changes, optionally accepting a new message. Refuses to amend pushed commits to prevent force-push risks.
/update-githubCommits uncommitted changes to git using Conventional Commits format, then pushes to the remote GitHub repository, with optional amend and no-verify flags.