commit-msg

name	commit-msg
description	Generate a JIRA-linked conventional commit message from staged git changes. Extracts ticket number from branch name (PRO-####, BUG-###), checks for new TODO comments, formats the message, and copies it to clipboard via pbcopy. Does not commit — output only.

Generate JIRA-Linked Commit Message

Analyze staged changes and generate a commit message with JIRA ticket number from the current branch.

IMPORTANT:

• DO NOT COMMIT - only output the commit message and copy it to clipboard
• DO NOT include any "Co-authored-by" or emoji signatures
• Generate clean, professional commit messages only

Steps:

1. Extract ticket number from branch

   • Run git branch --show-current to get current branch name
   • Look for these patterns in the branch name:
     • PRO-#### (e.g., PRO-1234)
     • BUG-### (e.g., BUG-123)
   • If no matching pattern found:
     • Proceed without ticket prefix
     • Do NOT suggest the user change their branch name
     • Simply generate a standard commit message

2. Analyze staged changes

   • Run git diff --cached to see only staged changes
   • If nothing is staged:
     • Assume user wants to commit all modified files
     • Run git diff to see all unstaged changes
     • Run git status --short to see all modified/new files
   • If this is the first commit (no HEAD exists):
     • Run git diff --cached --stat to see what files will be committed
   • For context on branch changes: