commitlisted

# Conventional-commit a change Generate a single-line Conventional Commit subject from the staged changes and commit. Subject only: no body unless the user asks. Never push. ## Step 1: Check what is staged ```bash git diff --cached --stat ``` - If something is staged, commit only that. - If nothing is staged, show `git status -sb` and ask whether to stage everything (`git add -A`) or specific files. Do not stage silently. ## Step 2: Read the change ```bash git diff --cached ``` Identify what actually changed (feature, bug fix, docs, refactor, tests, config) and the most-affected area (top-level dir, module, or file) to use as the scope. ## Step 3: Compose the subject Format: `type(scope): summary` - **type** (required): `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `build`, `ci`, `perf`, `style`. - **scope** (optional): the module or dir touched, e.g. `commit`, `readme`, `dialect`. Omit if the change is broad. - **summary**: imperative mood, lowercase, plain everyday developer English, no trailing period. Aim for <= 50 characters. Good: `feat(commit): add conventional-commit skill`, `fix: handle empty staged diff`, `docs: clarify install steps`. Avoid: vague summaries ("update stuff"), past tense ("added"), a capitalized or period-ended summary, or stacking multiple unrelated changes into one subject. **No issue-key prefix**: never prepend a JIRA/issue key such as `[CUBRIDQA-1432]` or `[CBRD-1234]` to the subject, even if the repo's existing commit history