conventional commit rewriter

The problem

Writing standardized commit messages is tedious, leading to inconsistent logs that break automated changelogs and make history hard to read. Developers often default to vague messages like "fixed bug" or "updates," losing the context of what actually changed.

What it does

• Converts informal developer notes or diff summaries into valid Conventional Commits.
• Identifies the correct commit type (feat, fix, refactor, etc.) based strictly on provided context.
• Formats breaking changes with the "!" indicator and appropriate footers without inventing migration details.
• Detects and suggests splitting multiple unrelated changes into separate commit messages.
• Flags ambiguity when the input lacks sufficient detail to determine a type or scope.

Why this beats prompting it yourself

Generic LLMs often hallucinate technical details, invent issue numbers, or guess commit types to appear helpful. This skill enforces strict anti-hallucination rules, ensuring your git history stays factual and your automated CI pipelines don't break due to malformed headers.

Use cases

• Turning a messy list of "last hour" changes into a structured set of commits.
• Standardizing commit messages across a team with varying levels of discipline.
• Ensuring breaking changes are properly flagged for automated semver tooling.
• Cleaning up a PR summary before merging into the main branch.

Known limitations

This is a text-rewriting utility. It cannot access your local repository, execute git commands, or analyze code unless the diff is explicitly pasted into the chat.