Commit
Use when the user asks to commit or stage changes (commit/stage/save/submit), when a task ends with dirty files to commit, or when multiple files should be split into logical commits.From its SKILL.md
npx -y skills add jukanntenn/grill-me-sleek --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.3 KB, as published. Nobody here has run it
Commit
Group by logical change, not by file. Draft a plan, confirm, then execute. Never push, never amend.
git status --porcelain+git log --oneline -5for current changes and history style.- Separate AI-edited files from unrecognized ones; list unrecognized separately, never mix them in.
- Group by logical unit (handler+db+test in server, page+component+types in web, cli flag+parse+help); a feature spanning server+web+cli is one unit when the parts are meaningless alone. Order:
build/chore→feat→fix→refactor→style→docs→test,releaselast. - Present the plan once; after confirmation run
git add+git commitbatch by batch. Rejected → stop. - Verify before each commit: run the touched package's tests (
cd server && cargo test,cd web|cli && pnpm test); the prek hooks (cargo fmt/clippy, eslint/tsc, prettier, sqlx-check) run ongit commit— never--no-verify. - Single file → skip the plan, commit directly.
Message: <type>(<scope>): <desc> — lowercase, imperative, no trailing period. Types: feat/fix/refactor/docs/test/chore/ci/build/style/perf/revert. Scopes: server/web/cli/e2e (components), docker/devops/github (infra); omit for root-level changes. Match the change's language.
- Generated files (
server/.sqlx/,pnpm-lock.yaml,Cargo.lock) bundle into the producing commit, or as a standalonechore— regenerate (python3 scripts/migrate.py prepare,pnpm install, cargo build), never hand-edit. - A migration, the
server/src/db/code that uses it, and the regenerated.sqlx/cache are one unit — the sqlx-check hook fails if they drift apart. - Version bump (plugin.json, marketplace.json, README badges) + CHANGELOG entry = one
chore: release vX.Y.Zcommit (see the release skill). - Template + code, and config + code, stay together when the code depends on them; mixed-language docs (
README.md+README_zh.md) one commit. - Never silently include unrecognized files. Never amend, never push, never placeholder messages (wip, update files).