timeline

Group git commit history into semantic development phases with Mermaid diagrams.

10|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/tykisgod/quick-question --skill timeline-tykisgod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: timeline
Source: https://github.com/tykisgod/quick-question/tree/main/skills/timeline
Command: npx skills add https://github.com/tykisgod/quick-question --skill timeline-tykisgod

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about timeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I group git commit history into phases for structured code review?

You can group git commit history into semantic development phases by automatically clustering commits based on feature affinity, natural breakpoints, and annotations, generating 5-10 logical phases for structured code review.

What is the best way to visualize architecture evolution from a git branch?

The best way to visualize architecture evolution is by generating an incremental timeline with Mermaid diagrams, which automatically renders structural changes per development phase to show how the codebase evolved.

How do I prioritize code review for a large game development branch with multiple features?

You can prioritize code review by generating a timeline with P0/P1/P2 risk annotations, file lists, and time estimates, allowing reviewers to focus on high-risk cross-module changes first and cutting review time.

Can I generate a consolidated review guide with reading order recommendations for 30+ commits?

Yes, you can generate a consolidated review guide that provides time estimates and reading order recommendations, specifically designed to help reviewers navigate large branches with 30+ commits spanning multiple modules.

Does semantic phase grouping work with merge commits and cross-module changes?

Semantic phase grouping works with merge commits and cross-module changes by applying feature affinity analysis and natural breakpoints to automatically cluster related commits into meaningful development phases.

When should I not use automated commit grouping for code review?

Automated commit grouping is not ideal for branches with very few isolated commits or linear single-feature changes, as the overhead of generating phased architecture timelines provides minimal value over reviewing raw diffs directly.