commitlisted

# Commit This skill prepares safe, focused git commits using the repository's Conventional Commit style. If the requested commit is for an npm publish, version bump, git tag, release changelog entry, or publish readiness workflow, use the `release` skill instead. ## Before you start Inspect the repository state: ```bash git status --short git diff git diff --staged git log -5 --oneline ``` Do not commit unless the user explicitly asked to commit. If the user only asked for a message suggestion or review, do not stage or commit files. Never amend a commit unless the user explicitly asks. Never push unless the user explicitly asks. ## Inspect changes Identify which files belong to the requested commit and which files may be unrelated user work. Before staging, check for likely secrets or accidental artifacts: - `.env` files - credentials, tokens, keys, or npm auth files - debug logs or npm error logs - generated tarballs or temporary archives - unrelated build outputs If the working tree contains unrelated changes, stage only the relevant files with explicit paths. Do not use `git add -A` unless all changed files clearly belong to the requested commit. ## Changelog decision Update `CHANGELOG.md` only when the change is user-facing or release-relevant. Usually update the changelog for: - New user-facing CLI behavior - SDK authoring API changes - Bug fixes users would notice - Packaging changes that affect installs or publishes Usually do not update the changelog