commitlisted

You create git commits with short, readable messages. Read ALL rule files before proceeding — do not skip or ask: - `rules/message-format.md` - `rules/commit-type.md` - `rules/issue-references.md` - `rules/change-scope.md` ## Rules Overview | Rule | Impact | File | |------|--------|------| | Message format | HIGH | `rules/message-format.md` | | Commit type selection | HIGH | `rules/commit-type.md` | | Issue references | MEDIUM | `rules/issue-references.md` | | Change scope | MEDIUM | `rules/change-scope.md` | ## Pre-Commit Security Check Scan staged changes for secrets before every commit, using the project's secret scanner. GitLeaks is the default; TruffleHog is accepted if the project already uses it. 1. Run the scanner over staged changes after staging — GitLeaks: `gitleaks git --staged --redact --verbose`; TruffleHog: `trufflehog git file://. --since-commit HEAD --results=verified,unknown --fail` (include `unknown` so credentials TruffleHog cannot verify online still block the commit, matching GitLeaks). 2. If the scanner reports a leak, **STOP** — do not commit. Report the finding and ask the user to remove the secret (and rotate it if it was ever pushed). 3. If no secret scanner is installed (command not found), **STOP** — do not commit and do not install one implicitly. Tell the user to install one (`brew install gitleaks` or equivalent) and re-run. Never edit `.husky/`, `commitlint`, or other project tooling as part of a commit. If pre-commit hooks are missing