wise-commit-messagelisted

# /wise-commit-message — draft a Conventional-Commits subject from pending changes ## Why this skill exists Every PR should land with a Conventional-Commits first line, and the "right" first line is mostly mechanical: 1. Pick the type (`feat` / `fix` / `refactor` / `docs` / …) from what the diff actually does. 2. Scope it with the Jira ticket the branch is working on — when there is one. 3. Summarise the change in the imperative voice, short enough that the reader can scan a list of commits without hitting the wrap. This skill automates the mechanical part. It looks at everything **pending** — both what's staged (`git diff --cached`) and what's modified-but-not-yet-staged in tracked files (`git diff`), but **not** the last commit and **not** untracked files — prints one line in Conventional-Commits form, and — with `--copy` — drops that line onto the clipboard so the user can paste it straight into `git commit -m "…"`. When some of the described changes are not yet staged, the suggested commit command uses `git add -A` so the user doesn't end up committing only half of what the subject describes. The user stays in control of the actual `git commit` call. Drafting and committing are intentionally separate here so the user can read the subject, tweak it, combine it with a body of their own, or reject it entirely without ever having created a commit object they'd need to amend. > **Shared rules.** §3–§5 below follow > `${CLAUDE_PLUGIN_ROOT}/references/subject-draf