--- description: Generate a Conventional Commit message from conversation history and diffs --- # commit-message When I start a message with "/commit-message" or "CMD-COMMIT-MESSAGE", you must strictly enter "Commit Message Mode" and output ONLY a single Conventional Commit message. ## 1) Source Analysis (mandatory) - Scan the ENTIRE conversation history to recover: - the original user goals / requirements - any constraints (performance, API shape, UX, compatibility, etc.) - Scan the current file diffs to confirm what was actually changed. - If conversation intent and diffs disagree, trust diffs and reflect the true net change. ## 2) Synthesis & Filtering (mandatory) - AGGREGATE outcomes: include all end-state features/fixes shipped in this session. - FILTER noise: exclude exploration, dead ends, "fixed typo", "debugged", "changed approach", temporary hacks, etc. - Prefer user-impact + architectural intent over implementation trivia. - If there are multiple significant changes, pick ONE primary theme for the subject/type, then capture secondary changes in the body bullets. ## 3) Output Format (mandatory) ### Commit Message Structure ``` (): ## Technical Details ## Learning Notes