commit-workflowlisted

# Commit Workflow Use a strict two-step process: prepare first, commit second. Keep all commit actions non-interactive and Git-native. ## Triggering and Invocation - Requests like `commit` or `do commit` are likely to trigger this skill via semantic matching. - For deterministic invocation, use explicit phrasing such as `Use $commit-workflow. ...`. - Two-step behavior is mandatory: - First prepare and approve the commit message. - Then execute the commit after explicit approval. Examples: - `Use $commit-workflow. Review changes and prepare commit message.` - `Use $commit-workflow. Commit now with the approved message.` ## Hard Rules - Do not use Claude slash commands such as `/commit-prepare` or `/commit-do`. - Do not invoke Claude CLI for commit workflow tasks. - Use non-interactive Git commands only. - Never commit before explicit user approval of the drafted message. - Never push automatically. ## Step 1: Prepare Commit Message 1. Run `git status --short` to inspect changed files. 2. Run `git diff` (or focused diffs) to inspect actual changes. 3. Run `git log -5 --oneline` to align with recent commit style. 4. Draft a commit message with these rules: - Subject line max 50 characters. - Imperative mood. - No trailing period in subject. - Exactly one blank line between subject and body. - Hard-wrap every body line to 72 characters or less. - Do not insert empty lines between body sentences. - Explain what changed and why. - Never include `Bump module version`. - Neve