What problem does it solve?
This Skill helps you consistently create standardized commit messages that comply with Guardia Lexis, including correct formatting, atomic change scope, language requirements, and GPG signing (when using the local path).
Core Features & Use Cases
- Conventional message composition: Guides you to choose a valid commit type and optional scope, then write an English imperative subject within 72 characters, optionally adding an English/local-language tagged body and standard footers.
- Lexis validation before committing: Enforces conventional format, small/atomic commits, language-tag rules, and signed-commit requirements.
- Authorship routing (human vs warriors-default-author): Uses directives to decide whether to create a remotely signed commit via a GitHub App token or to sign locally with GPG, including required fallbacks.
Real-world example: you finish a small, single-purpose refactor in your repository, want a Conventional Commits message (like fix/auth) with a clear rationale, and need the commit to be properly signed and validated against Guardia Lexis before you publish.
Quick Start
Use the kata-commit workflow to analyze your staged changes, generate a Conventional Commits message, validate it against the four Lexis rules, and then execute either the remote GitHub App commit or a local GPG-signed commit with final verification.
