Git Commit Message Generator

Degree of freedom: MIXED. Type/scope/subject wording [HIGH freedom]; stage-only-named-paths and never-push [LOW freedom — run exactly].

Create one clear, meaningful conventional commit. This skill owns deliberate staging + commit wording, not release preparation, pushing, or PR creation. The change must already be logically scoped.

How to reason

1. Scope — named files/hunks already decided; else stop
2. Type — feat/fix/docs/… from the actual diff
3. Subject — imperative, ≤50 chars, why in the body if needed
4. Bound — commit only; never push or open a PR

Worked example