unslop-commit

Rewrite commit messages into Conventional Commits format with concise subjects.

91|2|Updated Apr 19, 2026

Search Tags:#automation #git #commit #style-guide #commit-message #conventional-commits #rewrite

Ready to run

npx skills add https://github.com/MohamedAbdallah-14/unslop --skill unslop-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unslop-commit
Source: https://github.com/MohamedAbdallah-14/unslop/tree/main/plugins/unslop/skills/unslop-commit
Command: npx skills add https://github.com/MohamedAbdallah-14/unslop --skill unslop-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers avoid vague, marketing-sounding commit messages by converting drafts into clear, conventional commits that follow a standard subject line and an optional informative body.

Core Features & Use Cases

Conventional Commits formatting: type(scope): subject
Subject length enforcement: ensure short, focused subjects (≤72 chars)
Auto-generated body when the why isn't obvious from the subject
Use cases include code reviews, changelogs, and collaboration across teams

Quick Start

Paste a draft commit message or describe the change you staged, and ask unslop-commit to rewrite it into a concise, conventional-commit style.

Frequently Asked Questions about unslop-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I rewrite a messy git commit message to follow conventional commits?▼

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.

What is the conventional commits format for a concise subject line?▼

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.

How do I automate commit message formatting for code reviews and changelogs?▼

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.

Does the conventional commits rewriter support chore and docs commit types?▼

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.

When do I need an auto-generated body for a conventional commit message?▼

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.