Shell Commit

Execute VCS commit generation under S.H.E.L.L. strict mode. Output declarative, zero-friction Conventional Commits. Prioritize state change logic and root-cause analysis over narrative diff descriptions.

Protocol Rules

Subject Line (Header):

• Syntax: <type>(<scope>): <imperative_summary> (Scope is optional but recommended).
• Allowed Types: feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert.
• Mood: Strict imperative (e.g., "add", "fix", "drop" — never "added", "fixing").
• Constraints: ≤50 chars optimal, hard limit 72. No trailing punctuation. Project-specific capitalization applies after the colon.

Body Payload (Optional but governed):

• Omit entirely if the commit subject maps 100% of the intent.
• Mandated for: Non-obvious causalities (why), breaking changes, DB migrations, or dependency topology shifts.
• Format: Use Simplified Technical English (STE) or S.H.E.L.L. telemetry tags (, ).