Commit
Use this skill whenever the user asks you to create a git commit for the current work.
Instructions
- Review the current git state before committing:
git statusgit diffgit log -5 --oneline
- Only stage files relevant to the requested change. Do not include unrelated untracked files, generated files, or likely-local artifacts.
- Read and follow
.github/CONTRIBUTING.md#commit-messages. It is the source of truth for Ghost's commit conventions. - For publishable packages, check whether a release intent is required. A
package
README.mdis published and requires a release; repository-only Markdown such asAGENTS.md,CLAUDE.md, changelogs, and package-localdocs/does not. - Run
git status --shortafter committing and confirm the result.
Important
- Do not push to remote unless the user explicitly asks
- Keep commits focused and avoid bundling unrelated changes
- If there are no relevant changes, do not create an empty commit
- If hooks fail, fix the issue and create a new commit. Never bypass hooks.