unikit-commit

# {{engine_name}} Commit Generator Generate commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification, with {{engine_name}}-specific safety checks. ## Language Awareness — BLOCKING PRE-REQUISITE **BEFORE producing ANY output**, silently read `.unikit/system/LANGUAGE_RULES.md` and apply its rules to ALL subsequent output. If the file is missing or unreadable, fall back to English. Do not produce any user-facing output until language rules are loaded. Do not announce, confirm, or mention the language setting. ## Workflow 1. **Analyze Changes** - Run `git status` to see staged files - Run `git diff --cached` to see staged changes - If nothing staged, show warning and suggest staging 2. **{{engine_name}} Safety Checks** Run these checks before generating the commit message. Report findings as `WARN` or `ERROR`. **a) Engine companion files** Some engines require companion/metadata files for every asset. Read `.unikit/DESCRIPTION.md` to determine if the current engine has such a mechanism. If yes: - If a new file is staged, its companion is also staged (and vice versa) - If a file is deleted, its companion is also deleted (and vice versa) - Orphaned companion files (no matching asset) → `ERROR`, suggest staging the missing counterpart or removing the orphan - Missing companion for a new asset → `ERROR`, suggest staging it If the engine has no companion file mechanism — skip this check. **...