issue-progress-tracking

# Issue Progress Tracking

Automatic GitHub issue progress tracking that updates issues based on commits and marks sub-tasks as complete.

## Overview

- Working on GitHub issues with checkbox sub-tasks
- Making commits that reference issue numbers
- Using issue-prefixed branches (e.g., `issue/123-feature`, `fix/456-bug`)
- Wanting automatic progress visibility without manual updates

## How It Works

### Automatic Progress Tracking

The plugin automatically tracks your work through three coordinated hooks:

1. **Commit Detection** (`issue-progress-commenter.sh`)
   - Extracts issue number from branch name or commit message
   - Queues commit info for batch commenting
   - Supports patterns: `issue/123-*`, `fix/123-*`, `feature/123-*`, `#123`

2. **Sub-task Updates** (`issue-subtask-updater.sh`)
   - Parses commit messages for task completion keywords
   - Matches against unchecked `- [ ]` items in issue body
   - Automatically checks off matching tasks via GitHub API

3. **Session Summary** (`issue-work-summary.sh`)
   - Posts consolidated progress comment when session ends
   - Includes: commits, files changed, sub-tasks completed, PR link

### Issue Number Extraction

```bash
# From branch name (priority)
issue/123-implement-feature  # Extracts: 123
fix/456-resolve-bug          # Extracts: 456
feature/789-add-tests        # Extracts: 789
123-some-description         # Extracts: 123

# From commit message (fallback)
"feat(#123): Add user validation"     # Extracts: 123
"fix: Resolve bug (closes #456)"      # Extracts: 456
```

### Sub-task Matching

Commit messages are matched against issue checkboxes using:
- Normalized text comparison (case-insensitive)
- Partial matching for task descriptions
- Keyword detection (Add, Implement, Fix, Test, etc.)

**Example:**
```markdown
# Issue body
- [ ] Add input validation
- [ ] Write unit tests
- [ ] Update documentation

# Commit message
"feat(#123): Add input validation"

# Result: First checkbox auto-checked
- [x] Add i