git-commitlisted

# Purpose Generate conventional commit messages for staged changes: a `<type>(<scope>): <subject>` subject line, optional bullet body, optional `BREAKING CHANGE:` / `Closes #N` footer. Message generation only — no git operations are run. Scopes come from the project's `.claude/project.json` -> `commitScopes`. # Rules - NEVER generate a message when staged files may contain secrets (`.env`, `*.populated.yaml`, `credentials.json`, `*.key`, `*.pem`, `*secret*`). Refuse and instruct the user to unstage them — no exceptions, no confirmation prompt. - Subject: imperative mood, lowercase first word, no trailing period, max 72 characters, describing the user-visible change — never "update file X". - One commit message per repo. Never combine scopes like `feat(app,infra)`. - Never use a deprecated scope — map it to its documented replacement from the project's `CLAUDE.md`. - Add a `BREAKING CHANGE:` footer whenever the change breaks existing APIs, CLI flags, or port assignments. # Resources - Read `resources/procedure.md` when generating a message — the step-by-step procedure, inputs/outputs, security gate, self-check, and escalation rules. - Read `resources/format-reference.md` when picking type or scope — type/scope tables, subject rules, multi-scope handling, examples, failure modes. - Read `examples/commit-examples.md` for additional worked examples (it may contain deprecated legacy scopes such as `be`/`fe`/`helm` — always use current `commitScopes`). # How to use ## What i