What problem does it solve?
This skill eliminates the manual effort of reviewing large, multi-commit branches by automatically grouping commit history into logical development phases, so reviewers can build a clear mental model of how the codebase evolved without sifting through raw diffs.
Core Features & Use Cases
- Semantic Phase Grouping: Automatically groups commits from a base branch to HEAD into 5-10 meaningful development phases based on feature affinity, natural breakpoints, and commit annotations.
- Dual Review Document Generation: Creates an architecture evolution timeline with incremental Mermaid diagrams showing changes per phase, and a code review timeline with prioritized P0/P1/P2 risk items, file lists, and time estimates.
- Use Case: For a game development branch with 30+ commits spanning player systems, UI updates, and backend changes, this skill generates a structured review guide that lets reviewers focus on high-risk changes first, cutting review time significantly.
Quick Start
Use the timeline skill to generate phased architecture evolution and code review documents for your current git branch's commit history.