.rules

## Git Commits

Follow this repo's commit-message style. Output the raw commit subject only: no surrounding backticks, quotes, Markdown, bullets, or explanation. Use a concise Conventional Commit subject (`feat`, `fix`, `chore`, `docs`, `ci`, `refactor`) with an optional short scope, e.g. `fix(kernelcache): detect enosys syscalls by instruction pattern matching`. Keep it imperative and specific, describe the actual change instead of the file or a "style guide", and reserve `[skip ci]` for generated DB/key refresh commits that already follow that pattern. Do not use generic `Update <file>` subjects for normal authored changes; leave that style for mechanical generated-file churn.