SKILL.md

name	git-commit
description	Drafts and reviews git commit messages in Conventional Commits form, saying why over what, with the scope taken from the surrounding history. Review can also judge whether the change is atomic and consistent with the commits around it. Use when the user asks to draft a commit, write a message for a diff, review a commit message, run `git commit`, or commit and push.
license	MIT
metadata	argument-hint [lite|full|ultra] [push]

Git Commit

Draft and review Conventional Commits messages, saying why over what, at the cheapest effort level that does the job.

Registry

Name	Path
full	references/full.md
ultra	references/ultra.md

Effort levels gate history scanned and text produced. Default: full. Switch per invocation: /git-commit lite|full|ultra. Each level's name is its registered name; lite loads none, ultra loads full before its own.

Level	Behavior
lite	Subject line only; scope from staged paths; no history scan. Cheapest.
full	Scoped subject plus wrapped body and footer; scope resolved from recent history. Default.
ultra	Full, plus an atomicity and history-consistency audit before drafting.

Read ONLY the reference files the active level lists. The core rules below apply at every level.

Push Verb

push is a quick-ship action: stage as directed, commit, then push to the tracked remote, reporting the pushed range in one line. Without an explicit level, push implies lite; an explicit level wins, so full push and ultra push draft at that level first. Run git push ONLY when the user passed the push verb or asked to push.

(): Limit the entire subject line to 70 characters or fewer. Select a lowercase type from the allowed list. Enclose the optional lowercase scope in parentheses. Write the subject description in the imperative mood (e.g., Add, Fix, Refactor). Capitalize the first letter of the subject description. Terminate the subject line without a period. feat, fix, refactor, docs, style, perf, test, build, ci, chore, revert Derive the scope from the staged file paths: the single top-level directory, package, or module touched. Omit the scope when changes span several. Reuse a scope visible in `git log --oneline -10`; run no wider history scan. Output the subject line only. Add a body and footer solely for a breaking change, which always requires `BREAKING CHANGE: ` plus the migration path. Retain bot-authored commits and platform-generated merge commits exactly as they are; reformat nothing. Output strictly the raw commit text or the executable `git commit -m` command. Omit conversational filler, preambles, formatting acknowledgments, and concluding remarks.