Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From sorah-guides
Creates git commit(s) from staged/unstaged changes following sorah's commit style conventions. Use [split] arg for granular multi-commits with approval plan.
npx claudepluginhub sorah/config --plugin sorah-guidesHow this command is triggered — by the user, by Claude, or both
Slash command
/sorah-guides:commit [split]The summary Claude sees in its command listing — used to decide when to auto-load this command
Load the **commit-style** skill and follow its conventions precisely — subject line style, prefix pattern, contextful verbs, lowercase imperative, and body guidelines. ## Instructions Review all staged and unstaged changes, then create git commit(s). $ARGUMENTS ### When argument contains "split" Commit changes in logical, granular increments. Each commit should represent a single task or a functional unit. Ensure that the codebase remains stable and error-free at every commit point; do not commit code that is broken or fails to execute. Before committing, present the proposed split pl...
/commitAnalyzes staged git changes, generates a conventional commit message, seeks user approval, and executes the commit without trailers.
/commit-chunksAnalyzes local git changes and proposes splitting into multiple logical commits with messages and files. Commits all after user confirmation using git CLI.
/git-commitCreates conventional git commits with emojis, auto-stages unstaged files if needed, analyzes diffs, detects multiple logical changes, and suggests splitting into atomic commits.
/commitCreates clean, atomic git commits following project conventions. Supports ticket IDs, manual confirmation, and selective file commits.
/commitStages unstaged changes based on git status and diff analysis, then creates a commit with a generated message. Uses current branch and recent commit history for context.
/commitStages changes and commits locally using Conventional Commits format. Analyzes git status/diffs, drafts typed message with scope, confirms with user before git add and commit.
Share bugs, ideas, or general feedback.
Load the commit-style skill and follow its conventions precisely — subject line style, prefix pattern, contextful verbs, lowercase imperative, and body guidelines.
Review all staged and unstaged changes, then create git commit(s).
$ARGUMENTS
Commit changes in logical, granular increments. Each commit should represent a single task or a functional unit. Ensure that the codebase remains stable and error-free at every commit point; do not commit code that is broken or fails to execute.
Before committing, present the proposed split plan (which files/hunks go into which commit, with draft subject lines) and wait for approval.
Commit all changes together in a single commit.
If a git commit fails with gpg: signing failed: Inappropriate ioctl for device, ask the user to unlock their signing key. Do not skip or disable GPG signing.