--- name: workflow-git-commit description: > Create one conventional commit from an already-scoped change: stage named files/hunks, write the message, commit, never push. Use when "commit these files" or "write a commit message". Whole dirty tree to a merge-ready PR → workflow-release-prep. license: MIT --- # 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 > **Scope:** caller named `src/lib/cart.ts` and `src/lib/cart.test.ts` only. > **Type:** `fix` — deleted SKU no longer 500s. > **Subject:** `fix(cart): treat missing SKU as an invalid line` > **Bound:** staged those two paths, committed, did not `git push`. ## Self-critique before reporting - **No widen** — did not `git add .` / `-A` - **One concern** — mixed feat+fix was split or refused - **Conventional** — type + imperative subject, no trailing period - **Right owner** — whole dirty tree → `workflow-release-prep`; push/PR → `workflow-pr` ## Commit Format ``` ():