conventional-commitslisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Conventional Commits ## Scope Owns constructing a single-line commit subject that passes this repo's `commit-msg` and `beads-commit-msg` git hooks on the first attempt. It is not for: - Deciding whether to commit, what to stage, or how to split a diff (see `tool-git`). - Creating or managing beads issues (see `tool-br`); this skill only covers referencing an existing id in the message. - Body/footer content — the hooks here only validate the subject line. ## Inputs - The change being committed (already staged, or about to be). - An existing (or just-created) beads issue id — see `tool-br` to resolve or create one. ## Outputs - A single commit subject line that passes `commit-msg.py` and `beads-commit-msg.py` on the first attempt, with no `--no-verify` needed. ## Format ```text type(scope)!: description (issue-id[, issue-id...]) ``` - `type` — one of: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert. - `(scope)` — optional, lowercase-kebab-case, e.g. `(basicly)`. - `!` — optional, immediately before the colon, marks a breaking change. - `description` — required: **entirely lowercase, not just the first letter** — proper nouns and acronyms get lowercased too ("json", "conventional commits", not "JSON", "Conventional Commits"). Letters/digits/space/hyphen only — **no underscores** (write `test-cli`, not `test_cli`) and no other punctuation. No