conventional-commitslisted

# Conventional Commits Create commits and PR titles that are easy to review and pass `cog verify`. ## Required format Use Conventional Commits: ```text type(scope): imperative subject ``` The scope is optional: ```text fix: handle empty setup files feat(setups): add rust CLI preset docs(readme): clarify setup install commands ``` ## Allowed types - `feat` - user-facing feature or capability - `fix` - bug fix - `refactor` - code change without behavior change - `docs` - documentation only - `test` - tests only - `chore` - maintenance without runtime behavior change - `build` - build tooling, dependencies, or packaging - `ci` - CI workflow changes - `perf` - performance improvement - `style` - formatting only, not visual UI changes - `revert` - revert a previous change ## Subject rules - Use imperative mood: `add`, `fix`, `remove`, `rename`; not `added`, `fixed`, `removes`. - Start lowercase after the colon. - Do not end with a period. - Keep the first line under 72 characters when possible. - Describe the intent, not the file names. ## Commit workflow 1. Inspect the working tree: - `git status --short` - `git diff --stat` - `git diff` 2. Decide commit boundaries. - Split unrelated changes into separate commits. - Split behavior, tests, docs, formatting, dependencies, and generated files when they are reviewable separately. - If one file has mixed changes, use patch staging. 3. Stage only intended changes. - Use `git add <path>` for clean file