Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From ship
Analyzes staged Git changes, generates a Conventional Commits message, and executes the commit. Accepts optional context or issue reference.
How this command is triggered — by the user, by Claude, or both
Slash command
/ship:SKILL [context or issue reference]haikucommit/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /commit - Git Commit Execution Analyze the staged Git changes, generate a Conventional Commits format message, and run the commit. ## Input `$ARGUMENTS` may contain context or an issue reference. Trim whitespace; if empty, analyze staged changes only. If non-empty, treat it as a hint for the message scope or footer. ## Execution 1. Run `git status` and `git diff --staged` in parallel to read the staged changes 2. Generate one message from the changes and `$ARGUMENTS`, following Type Detection and Rules 3. Run the commit directly via the sandbox-compatible commit ## Type Detection I...
Analyze the staged Git changes, generate a Conventional Commits format message, and run the commit.
$ARGUMENTS may contain context or an issue reference. Trim whitespace; if empty, analyze staged changes only. If non-empty, treat it as a hint for the message scope or footer.
git status and git diff --staged in parallel to read the staged changes$ARGUMENTS, following Type Detection and RulesInfer type from diff context. Default to feat if unclear.
| Type | When to use |
|---|---|
| feat | New functionality or capability |
| fix | Bug fix or error correction |
| refactor | Code restructuring without behavior change |
| docs | Documentation only changes |
| test | Adding or updating tests |
| chore | Config, dependencies, maintenance |
| perf | Performance optimization |
| style | Formatting, whitespace, linting |
| ci | CI/CD configuration changes |
Subject is ≤72 chars, imperative, lowercase, no period. Footer uses BREAKING CHANGE: / Closes #123 / Co-authored-by:.
feat(auth): add OAuth2 authentication support
feat(api)!: remove deprecated endpoints # BREAKING CHANGE
cat > /tmp/claude/commit-msg.txt << 'EOF'
<message>
EOF
git commit -F /tmp/claude/commit-msg.txt
mv /tmp/claude/commit-msg.txt ~/.Trash/ 2>/dev/null || true
| Error | Action |
|---|---|
| No staged files | Report "Nothing staged" |
| Empty diff | Return minimal message |
| No git repository | Report "Not a git repo" |
| Pre-commit failed | Report hook error |
Report the executed commit in one line.
npx claudepluginhub thkt/dotclaude --plugin ship/commit-msgGenerates a Conventional Commits-compliant commit message from staged git changes. Infers scope from file paths or accepts an optional scope argument.
/commitAnalyzes staged Git changes to generate an intelligent conventional commit message with type, scope, body, and footers; presents for review and commits if approved.
/commitAnalyzes git diffs or staged changes and generates conventional commit messages explaining the motivation behind the change. Also supports analyzing, staging, and validating commits.
/commitAnalyzes staged git changes and generates a structured semantic commit message with conventional commit type, concise subject, and detailed body.
/commitAnalyzes staged git changes, generates a conventional commit message, seeks user approval, and executes the commit without trailers.
/commitCreates a conventional git commit by analyzing staged changes and auto-generating a message in 'type(scope): description' format. Optional scope or message hint.