Skill

commit

Use when creating a git commit.

Stars

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/pi-stuff:commit

User invocable

Model invocable

Inline context

Default effort

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Create a git commit using Conventional Commits format.

22 lines · ~313 tokens

Stats

LanguageTypeScript

Stars1

MaintenanceExcellent

Last CommitJun 23, 2026

Actions

Stats

Actions

Infer from the prompt whether the user provided file paths, globs, or additional instructions.
Review git status --short and git diff to understand the current changes. Limit inspection to the provided file paths or globs when present.
Optionally run git log -n 50 --pretty=format:%s | grep -E '^[a-z]+\([^)]+\):' to identify commonly used commit scopes.
Determine the intended changes:
- If the user provided file paths or globs, use only those paths.
- If the user did not provide file paths or globs, use all current changes.
- If there are no intended changes to commit, do not create a commit. Report that there is nothing to commit.
- If there are unrelated, ambiguous, generated, or risky changes, ask for clarification before committing.
Stage only the intended changes.
Review git diff --staged and create a Conventional Commits message based only on the staged diff.
Run git commit -m "<subject>" and include -m "<body>" only when a body is useful.
Run git status --short and git log -1 --oneline after committing, then report the commit hash and message.