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-guides[split]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...
/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.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitRuns pre-commit git checks, quality gates (lint, typecheck, tests), code review for issues; drafts conventional commit message; stages specific files and commits. Supports --no-verify, --amend, --push options.
/commitAnalyzes current git diff, generates 3 conventional commit message options (concise, detailed, comprehensive), presents for user selection, and executes git commit.
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.