gh-commit

Context-Aware Commit

Smart commit workflow that classifies changes, flags out-of-context modifications, and supports multiple atomic commits.

Tool Usage: This workflow uses the AskUserQuestion tool for interactive decisions about change inclusion.

Phase 1: Context Discovery

1. Get current branch and linked issue:

   BRANCH=$(git branch --show-current)
   ISSUE_NUM=$(echo $BRANCH | grep -oE 'issue-[0-9]+' | grep -oE '[0-9]+')
   

2. Fetch linked issue details (if found):

   gh issue view $ISSUE_NUM --json title,body,labels 2>/dev/null
   

3. Get branch diff summary:

   git diff --name-only main...HEAD
   

Phase 2: Change Analysis

1. Get all changes:

   git status --porcelain
   

2. Classify each change:

   In-Context (confident):

   • Files already in branch diff
   • Files matching issue keywords
   • Same directory as other changes

   Uncertain (needs review):

   • Related directories but not in diff
   • Documentation files

   Out-of-Context (flagged):

   • Config files (.env, editor settings)
   • Unrelated feature directories
   • Auto-generated files

3. Display classification:

   ## Change Classification
   
   **Context**: Branch `{branch}`, Issue #{issue}: "{title}"
   
   ### In-Context
   - src/api/users.ts (matches issue keywords)
   
   ### Uncertain
   - docs/api.md (documentation)
   
   ### Out-of-Context
   - .vscode/settings.json (editor config)
   

Phase 3: Interactive Planning

Use the AskUserQuestion tool if uncertain or out-of-context files exist:

• Option 1: "Commit in-context files only" (Recommended)
• Option 2: "Include uncertain files"
• Option 3: "Select specific files"
• Option 4: "Commit all files"

Phase 4: Commit

1. Stage selected files:

   git add {selected_files}
   

2. Generate commit message following conventional format:

   • feat: for features
   • fix: for bug fixes
   • docs: for documentation
   • test: for test changes
   • refactor: for refactoring
   • chore: for maintenance