What problem does it solve? Inconsistent commit messages, skipped pre-commit hooks, and lost verification work make git history hard to review and audit. This Skill enforces disciplined commit practices so every change is traceable and reviewable. ## Core Features & Use Cases - Conventional Commit Messages: Writes commit messages using conventional-commit prefixes (feat, fix, chore, docs, refactor, style, test, build, ci, perf, revert) without scopes, focusing on the why rather than the what. - Hook Enforcement: Never passes --no-verify or -n, ensuring linting and pre-commit hooks always run. - Vendored Code Workflow: Commits ported or copied code as a pristine raw copy first, then applies integration edits as a separate commit so reviewers can diff against the original. - Verification Code Records: Commits temporary debug or test code and its revert as separate commits, preserving a citable record in git history. - Use Case: When porting a utility module from another repository, commit the untouched copy first, then commit your adaptations separately so the reviewer sees exactly what changed. ## Quick Start Commit my staged changes following the custom git committing conventions and report the commit hash.