commit
Generate a Conventional Commits message, commit, and optionally push to remote.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- commit
- description
- Generate a Conventional Commits message, commit, and optionally push to remote.
- when-to-use
- user wants to commit changes or write a commit message -- '/commit', 'commit this', 'make a commit', 'git commit', 'commit my changes'
- argument-hint
- [--push] (auto commit & push without prompting)
02 资源文件 1
- 参考文档TEST-PLAN.md2.4 KB
03 SKILL.md 正文
Gather Git Context
!`git rev-parse --is-inside-work-tree 2>/dev/null || echo "NO_GIT"`
!`git status --short 2>/dev/null || echo "NO_GIT"`
!`git diff --cached 2>/dev/null || echo "NO_GIT"`
!`git log --oneline -10 2>/dev/null || echo "NO_COMMITS"`
Instructions
Step 0 -- Git Availability
If any gather-context block above returned NO_GIT, this directory is not a git repository.
Print: > No git repository detected. /commit requires a git repo.
Stop here.
Silently determine which case applies — do not show the case label or decision logic to the user:
- No changes: If
git statusis empty → tell the user and stop. - Nothing staged: If
git diff --cachedis empty butgit statusshows changes → tell the user to stage files and run/quiver:commitagain, then stop. - Staged changes exist: Proceed silently to Commit Message Generation.
Commit Message Generation
Analyze git diff --cached and the recent log. Generate a Conventional Commits message following these rules:
Type — Select one based on primary intent:
| Type | When to Use |
|---|---|
feat |
New feature or capability visible to users |
fix |
Bug fix |
docs |
Documentation only (README, comments, JSDoc) |
style |
Formatting, whitespace, semicolons — no logic change |
refactor |
Code restructuring with no behavior change |
perf |
Performance improvement |
test |
Adding or fixing tests |
build |
Build system or external dependencies (npm, Makefile) |
ci |
CI/CD configuration (GitHub Actions, CircleCI) |
chore |
Maintenance tasks (version bumps, tooling config) |
revert |
Reverting a previous commit |
Scope — From file paths: single directory → its name, single file → domain name, cross-cutting → omit.
Breaking changes — If the change removes/renames public APIs, changes signatures, alters data formats, or removes CLI flags/commands, add ! after type/scope and a BREAKING CHANGE: footer.
Subject line — Imperative mood, lowercase after colon, no period, ≤72 chars total, describe what not how.
Body — Almost never. Only for breaking changes or when the subject alone would be misleading. Wrap at 72 chars. Never include file lists — git log --stat shows this.
Footers — BREAKING CHANGE: if applicable. Refs: #issue if relevant.
Include a body or footers only for breaking changes or multi-type changes where the subject alone is genuinely ambiguous. Default to subject-only. Don't add Co-authored-by or attribution footers unless explicitly requested.
Output
Important: The user must see the full commit message before answering the prompt. Print it to the chat stream and keep the AskUserQuestion question itself to one short line -- see Default (no flag) below.
Flag: --push
If $ARGUMENTS contains "push" (e.g., /quiver:commit --push), skip the AskUserQuestion step entirely. Instead, show the generated commit message, then immediately execute Commit & Push (commit + push to remote) without prompting.
Default (no flag)
Two steps, both mandatory: print the message, then ask. Do not paste the commit message into the AskUserQuestion question field -- that field is rendered as a single truncated line by some Claude Code surfaces, so a multi-line message is cut off or dropped entirely and the user is asked to approve something they cannot read.
Step 1 -- print the message as normal chat output, verbatim inside a fenced block, so the user sees exactly what git commit will receive:
{type}({scope}): {subject}
{body lines, if the message has a body}
Step 2 -- ask, and wait for the answer:
- Question:
"Commit this?"-- one short line. No newlines, no message text, no ANSI escape codes.AskUserQuestionrenders the question in a TUI box that prints escape sequences literally instead of styling them. - Header: "Action"
- Options:
- Commit — "Commit with this message"
- Commit & Push — "Commit and push to remote"
- Edit — "Revise the message"
- Cancel — "Abort without committing"
Printing the message is not approval. It is only the readable copy of what the prompt is about, and it exists because the prompt cannot display it. Never run git commit without an answer from this AskUserQuestion. The user asking for a commit in their message is not the answer either -- that is what put the skill on this step. --push is the only path that skips the prompt.
Commit Execution
On commit or commit & push:
- Commit using a HEREDOC:
git commit -m "$(cat <<'EOF' {full commit message} EOF )" - Verify:
git log --oneline -1andgit status --short.
If commit & push, also:
- Detect branch:
git branch --show-current - Push: if
git rev-parse --abbrev-ref @{upstream} 2>/dev/nullsucceeds →git push, otherwise →git push -u origin {branch} - Verify push exit code is 0.
Output:
Committed:
{short hash}{subject} Branch:{branch name}Pushed to:origin/{branch}(only if pushed)
On edit: Ask what to change, revise, re-present, and ask again.
On cancel:
Commit cancelled. Staged changes are intact.
Stop here.
Error Handling
If git commit fails, show the error verbatim and suggest the user fix the issue and re-run /quiver:commit. Never retry automatically or use --no-verify.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.