Commit

commit

Fast path to commit. Inline context is already gathered below — prefer it over extra tool calls. Reason about file safety and scope, then commit.

Arguments

$ARGUMENTS may be empty or contain directives. Recognize and combine:

| Directive | Behavior | | ----------------------------- | -------------------------------------------------------------------------------------- | | only staged / staged only | Do NOT stage anything. Commit the existing index. | | relevant / scoped | Stage only files that fit the current task's scope; leave unrelated tweaks out. | | amend | Use git commit --amend --no-edit after staging. Do not rewrite the existing message. | | no trailer | Never append a Co-Authored-By trailer, even if the repo uses them. | | anything else | Treat as a message hint or additional constraint. |

Current state

Branch: !git branch --show-current

Status:

!`git status --short`

Unstaged diff (stat):

!`git diff --stat`

Staged diff (stat):

!`git diff --cached --stat`

Last 5 commits:

!`git log --oneline -5`

Last commit message (for trailer style):

!`git log -1 --format='%B'`

CLAUDE.md / AGENTS.md commit conventions (if any):

!`grep -B 1 -A 10 -i "^##.*commit\|commit message\|commit format\|conventional commit" CLAUDE.md AGENTS.md .github/CONTRIBUTING.md 2>/dev/null | head -80 || echo "(none found — use conventional commits)"`

Staging rules

Source code, docs, and tracked configs are safe by default — don't overthink them. Focus the skip judgement on generated and machine-specific artifacts.

Never auto-stage these:

• Build or incremental artifacts: *.tsbuildinfo, dist/, build/, out/, .next/, .turbo/, .parcel-cache/, coverage/, node_modules/
• Caches and logs: .cache/, *.log, logs/, npm-debug.log*, pnpm-debug.log*, yarn-debug.log*
• OS / editor cruft: .DS_Store, Thumbs.db, *.swp, *.swo, *~
• Secrets: .env, .env.* — warn the user if they appear untracked
• Local machine state: .playwright-mcp/, .claude/settings.local.json, .vscode/settings.json unless already tracked

Anything else — use judgement. If a path looks generated (hash suffix, inside a cache-like dir, editor backup) and is untracked, skip it and list it in the final report. If ambiguous, ask by skipping and reporting, not by prompting.

Never use git add ., git add -A, or git add -f. Stage with explicit paths.

Heavy-diff delegation

The injected git diff --stat blocks above show the size. Handle the common case in-thread. Only delegate when the staged OR unstaged diff exceeds ~500 changed lines or ~20 files AND you need actual diff content (not just stats) to decide scope, classify files, or compose the body.

When delegating, dispatch one subagent:

• subagent_type: Explore
• Fork has no conversation history — pass the exact git diff output (or the

subset you need) in the prompt.

• Ask a single narrow question. Good shapes:
• "From this diff, which files belong to scope: ``? Return file paths only."
• "Summarize the distinct changes in this diff as 3-5 past-participle bullets, no prose."
• Use the returned answer directly. Do not ask the subagent to write the

commit message — that stays in-thread with full project context.

Do not delegate for small diffs. The round-trip is slower than reading the diff inline, and the main thread already has the conventions context.

Steps

1. Parse $ARGUMENTS.
2. If only staged: go to step 4.
3. Stage safe files with git add . Apply the rules above.

• If relevant: from the unstaged diff, pick only files whose changes fit

the scope described in $ARGUMENTS or obvious from the combined diff; leave the rest.

1. Look at the staged diff (git diff --cached --stat is already above; read

git diff --cached only if the message needs detail beyond the stat). If nothing is staged, stop and tell the user.

1. Compose the commit message:

• Single-line title, ≤72 chars, : .
• Types: feat, fix, docs, chore, refactor, test, style, ci.
• Follow the project convention from the grep block when present.
• If the current branch is issue-, append # to the title.
• Body only if the diff spans 3+ distinct changes: 2–4 short lines,

past participle, no bullets.

• Trailers: only include Co-Authored-By if the last commit already uses

one. Never add promotional footers.

1. Commit:

```bash git commit -m "$(cat

EOF )" `` If amend was requested: git commit --amend --no-edit`.

1. Never pass --no-verify. If a pre-commit hook fails: fix the issue, re-stage,

create a NEW commit (do not amend unless the user asked).

1. Final output: one line — Committed on : —

followed by a short skipped: … list if anything was left out.

Out of scope

• Pushing, opening PRs, switching branches.
• Splitting into multiple commits.
• Rewriting history beyond a single --amend --no-edit.
• Adding files listed in .gitignore via -f.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: edloidas
• Source: edloidas/skills
• License: MIT

Install and usage instructions live in the source repository linked above.