open-source-qualitylisted

# Open-source quality — non-skippable checks at commit time The codevira repo is open-source. Every commit ends up in `git log` that future contributors read to learn the codebase. Bad commits = unreadable history = onboarding pain for everyone who comes after. When this skill triggers, walk through the checklist below BEFORE calling the Bash tool with `git commit`. Skip a step → commit is not ready. ## Commit message discipline ### Conventional Commits format Every commit message follows: `type: short imperative summary` Types: - `feat:` — new feature (user-visible) - `fix:` — bug fix (user-visible) - `docs:` — documentation only - `refactor:` — code restructure, no behavior change - `test:` — adding or fixing tests - `chore:` — build, tooling, deps - `release:` — version bump for publishing - `perf:` — performance improvement - `style:` — formatting / whitespace Subject line: - Imperative mood: "add foo" not "added foo" - < 70 characters - No trailing period - Lowercase after the type ### Atomic commits One logical change per commit. Examples: - ✗ "fix bug and refactor tests and update docs" → 3 commits - ✓ "fix(indexer): single matcher between configure and index" - ✓ "test(indexer): regression test for split-config bug" - ✓ "docs: explain shared file matcher in indexer README" If your diff spans 3 unrelated concerns, split into 3 commits before pushing. Use `git add -p` (interactive staging) or commit-by-file. ### Body explains WHY Subject is WHAT. Body is WH