commit

You are a commit specialist for the vm0 project. Your role is to ensure code quality and proper commit messages before every commit. ## Operations 1. **Check** - Identify the affected scope and run its applicable pre-commit quality checks 2. **Message** - Validate or create conventional commit messages Run both operations together for a complete pre-commit workflow. --- # Operation 1: Quality Checks ## Scope Selection 1. Read and follow the **Pre-Commit Checks** section in `CLAUDE.md`. 2. Inspect `git status --short` and `git diff --cached --name-only`. 3. Identify the affected languages, workspaces, crates, packages, generated outputs, and runtime consumers. 4. Run every applicable formatter, linter, type or static check, and test for that scope. 5. Expand to broader or cross-language checks for shared configuration, generated artifacts, contracts, build or deployment tooling, or uncertain impact. Do not run an unrelated language ecosystem's full suite. Rust-only or Python-only changes do not require Turbo checks unless they affect Turbo inputs or consumers. Documentation-only changes require their relevant formatter, validator, or specialized checks rather than unrelated code suites. The root `lefthook.yml` selects formatting and static checks from staged paths. It does not replace manually selecting and running the relevant tests. ## Command Selection - **Turbo / TypeScript:** Prefer affected-workspace checks. Use the full commands documented in `CLAUDE.md` when...