Conventional Commit Message Workbench

How to use Conventional Commit Message Workbench

Inspect a Conventional Commit message or build a separate commit-message artifact from explicit JSON fields. Separate the type, scope, bang marker, body and footer candidates, keep multiline footer values, and distinguish uppercase breaking-change footers from ordinary text.

1. Provide commit message or builder json.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 50 KB of valid UTF-8, 2,000 lines, a 32-character ASCII type and 100 footers. A scope is bounded text without parentheses or line breaks. Header and body are separated by a blank line.
• The first footer-shaped line at the start of a later paragraph begins the footer block in this explicit parsing profile. Free-form body text can be ambiguous; review the reported split. Builder bodies and multiline values refuse ambiguous embedded footer starts.
• Types and ordinary footer tokens are compared case-insensitively where relevant. BREAKING CHANGE and BREAKING-CHANGE require uppercase. Semantic correctness of feat/fix or the actual diff is not inferred.
• The conventional release signal is descriptive and does not select or publish a version. No Git repository, commit, hook, command or release process is opened or modified.
• Inputs are processed on this device and are not automatically saved or uploaded.