Menu
Write a Conventional Commits message from a description of code changes. Use when the user asks for a commit message or describes a diff.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Turn a list of commits or changes into a release changelog (Keep a Changelog format). Use when preparing release notes.
Weigh options against weighted criteria to support a decision. Use when the user is choosing between alternatives.
Proofread and tighten text — fix grammar, clarity, and tone — and show what changed. Use when the user wants writing improved.
Build and explain a regular expression from a description, with examples. Use when the user needs a regex or wants one explained.
Answer a question with a short, sourced research brief. Use for "research X", "what's the latest on Y", or fact-finding that needs citations.
Write a SQL query from a plain-English request and a table schema. Use when the user wants a query written, explained, or fixed.
| name | commit-message |
| description | Write a Conventional Commits message from a description of code changes. Use when the user asks for a commit message or describes a diff. |
| license | MIT |
Produce a commit message in Conventional Commits format from the user's description of the change.
Format:
<type>(<optional scope>): <concise summary in imperative mood>
<optional body: what changed and why, wrapped at ~72 cols>
Allowed types: feat, fix, docs, style, refactor, perf, test, build, ci, chore.
Rules:
! after type/scope for a breaking change and add a BREAKING CHANGE: footer.