Conventional Commit

This skill is guidance, not a script. Describe one coherent engineering change using Conventional Commits. Read the actual intended diff first; the original task title may no longer describe it.

When not to use

• Organizing the work itself into reviewable slices. Use plan.
• Deciding whether a change is safe or complete. Use code-review.
• A request for a commit message with no intention to commit; a message request authorizes no Git mutation.

Inputs and authorization

• Required: the actual intended diff, not the original task title.
• Authorization: drafting a message authorizes no Git mutation. Committing requires an explicit request; inspect the exact staged content and preserve unrelated user work. Commit permission does not extend to push or history rewriting.

Method

Implementation, tests, and related documentation can share one intent. Split independent changes when doing so improves review or reversal, not merely because files have different types. Do not force coupled edits into broken intermediate commits.