Conventional Commits

Core Question

What Conventional Commit message accurately describes the exact change evidence provided, without expanding scope or claiming unsupported impact?

When To Use

Use this skill when the user asks to:

• write or revise a Conventional Commit message,
• validate an existing commit message,
• choose a commit type, scope, subject, body, or footer,
• express a breaking change using ! or BREAKING CHANGE:,
• generate a message from staged diff or from explicitly provided diff evidence.

When Not To Use

Do not use this skill to stage files, unstage files, create commits, split commits, or decide atomic boundaries.