context-progress

# Update Project Progress

This skill guides you through updating the context-progress branch to reflect current project status.

## When to Use

Use this skill when:
- Completing a significant task or milestone
- Starting new work that should be tracked
- Updating project status after a development session
- The user requests to "update progress" or "track status"

## Why context-progress Branch?

The context-progress branch uses a unique approach:
- **Stable Reference**: CLAUDE.md references the branch name, not a commit hash
- **Mutable State**: Progress changes frequently, so we amend one commit rather than creating many
- **No Hash Updates**: Avoids needing to update CLAUDE.md constantly
- **Clean History**: Keeps the main branch clean from progress tracking commits

## Auto-Extraction (Recommended)

The auto-extraction feature automatically generates structured progress content from your git history,
inspired by the `/compact` tool's extraction patterns.

### Quick Start

```bash
# Preview what will be extracted (no changes made)
~/.claude/plugins/context-commit/hooks/update-progress.sh --preview

# Update with auto-extraction (opens editor for review)
~/.claude/plugins/context-commit/hooks/update-progress.sh

# Update without editor (for CI/automation)
CONTEXT_SKIP_EDIT=1 ~/.claude/plugins/context-commit/hooks/update-progress.sh
```

### What Gets Auto-Extracted

| Category | Description | Source |
|----------|-------------|--------|
| **Commits** | Categorized by type (feature, fix, test, refactor) | `git log` since last update |
| **File Changes** | Added, modified, deleted files with stats | `git diff --name-status` |
| **Issues Resolved** | Commits containing "fix", "resolve", etc. | Commit message parsing |
| **Key References** | Functions, classes, structs added | Diff analysis |

### Merge Modes

Control how auto-extracted content merges with existing progress:

```bash
# Smart merge (default): preserve your manual "In Progress" and "Planned" edits
CON