unslop-commit

You can rewrite a messy git commit message by pasting the draft text or describing the staged change. The Skill converts it into the conventional commits format, utilizing a type(scope): subject structure with an optional body explaining the rationale.

The conventional commits format requires a type(scope): subject structure. It enforces imperative mood, disallows template prefixes, and caps the subject length at 72 characters to ensure deterministic, human-readable commit messages.

Automate commit message formatting by triggering the Skill with commands like /commit or pasting draft messages directly. It removes marketing jargon and applies deterministic conventional commits formatting suitable for changelogs and team collaboration.

Yes, the conventional commits rewriter supports chore and docs commit types alongside features and fixes. It processes software development workflows to ensure messages remain deterministic and free of marketing jargon across all supported types.

You need an auto-generated body for a conventional commit message when the reason for the change is not obvious from the subject line alone. The Skill adds this optional body to provide necessary context for code reviews and team collaboration.