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 ([INFO], [WARN]).
• Constraints: Wrap at 72 chars. Use - for structural lists.
• Metadata: Map trackers at EOF (Closes #42, Refs #17).

Syntax Blacklist:

• Conversational phrasing: "This commit does X", "I", "we", "now", "currently".
• Redundancy: Restating the diff or the filename if the scope already defines it.
• Attributions: "Generated by AI" or similar metadata.
• Embellishments: Emojis (unless explicitly mandated by local project CI/CD hooks).

Telemetry Examples

Scenario: New endpoint for user profile to reduce payload size.

• ❌ "feat: add a new endpoint to get user profile information from the database"
• ✅

  feat(api): add GET /users/:id/profile
  
  [INFO] Client payload optimization.
  Mobile bandwidth overhead high during cold-launch.
  Resolution: Expose isolated profile data, bypassing full user hydration.
  
  Closes #128