name	commit
description	Create a conventional commit. Use when user says "commit", "make a commit", or "save changes". NOT for: drafting code, running tests, or anything that changes files — this skill only stages and commits already-finished work.
model	sonnet
allowed-tools	["Bash(git add:)","Bash(git commit:)","Bash(git status:)","Bash(git diff:)"]
argument-hint	[optional commit message override]

<git_status> !git status --short </git_status>

<staged_diff> !git diff --cached </staged_diff>

Review the staged diff above.
Write a Conventional Commit message: feat: / fix: / chore: / docs: / refactor: / test: / perf:
If $ARGUMENTS is provided, use it as the commit subject.
Format: <type>(<optional-scope>): <subject> — subject under 72 chars.
Run: git commit -m "<message>"
Run: git status to confirm clean state.
Output the commit hash and message.

name	commit
description	Create a conventional commit. Use when user says "commit", "make a commit", or "save changes". NOT for: drafting code, running tests, or anything that changes files — this skill only stages and commits already-finished work.
model	sonnet
allowed-tools	["Bash(git add:)","Bash(git commit:)","Bash(git status:)","Bash(git diff:)"]
argument-hint	[optional commit message override]

<git_status> !git status --short </git_status>

<staged_diff> !git diff --cached </staged_diff>

Review the staged diff above.
Write a Conventional Commit message: feat: / fix: / chore: / docs: / refactor: / test: / perf:
If $ARGUMENTS is provided, use it as the commit subject.
Format: <type>(<optional-scope>): <subject> — subject under 72 chars.
Run: git commit -m "<message>"
Run: git status to confirm clean state.
Output the commit hash and message.

commit

安装方式