What problem does it solve? Writing consistent, well-scoped git commits is error-prone: changes get lumped together, message formats drift from the project history, and broken code gets committed without running tests. This Skill enforces a deterministic procedure so the same diff always produces the same commit structure. ## Core Features & Use Cases - Logical change grouping: Splits or joins changes based on build and test independence, keeping tests with the code they cover. - Conventional Commits formatting: Selects the correct type (feat, fix, docs, refactor, test, style, build, chore) and derives the scope mechanically from domain folders. - Pre-commit validation: Runs pnpm test and pnpm typecheck before committing and refuses to commit on failure. - Use Case: After finishing a feature touching src/economy/ plus its tests, ask the assistant to commit; it inspects the diff, groups the changes, writes a Spanish imperative message like "feat(economy): añade cálculo de impuestos", validates, and commits. ## Quick Start Ask the assistant to review the current git changes and create properly grouped Conventional Commits following this repository's commit procedure.
