helping-with-commits

Conventional Commits automate commit message structure with a standardized format: type(scope): description. This Skill generates compliant messages for your code changes, validates formatting, linting, and tests before committing, then prompts for approval—reducing manual review cycles and keeping your commit history consistent.

Before committing, the Skill enforces format validation, linting checks, test execution, and i18n comparison to catch issues early. It prevents commits with failing checks and secrets, ensuring only validated changes reach your repository.

Yes. The Skill applies project scopes—arcade, i18n, ui, a11y, perf, pwa, test, and deps—to categorize changes. It handles single-domain commits, multi-domain changes, and creates one logical commit per change while maintaining scope consistency across your codebase.

For multi-domain changes, the Skill analyzes your modifications across scopes and either consolidates them into a single commit with appropriate scope notation or splits them into separate logical commits, each following Conventional Commits rules for that domain.

The Skill generates commit messages automatically based on your code changes and project scopes, then presents them for your review and approval before committing. You control the final decision without manual message composition.

The Skill includes secret-detection as part of its pre-commit validation pipeline. It blocks commits containing secrets, flagging them during the approval step so you can remove sensitive data before the commit reaches your repository.