talk-stage2-research

Cross-reference git history with Stage 1 summary and CHANGELOG to produce an auditable timeline.

Updated May 30, 2026
One-click install
npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill talk-stage2-research-alexica00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: talk-stage2-research
Source: https://github.com/alexica00/claude-code-ultimate-guide/tree/main/examples/skills/talk-pipeline/stage-2-research
Command: npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill talk-stage2-research-alexica00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps researchers and presenters ensure that Stage 2 metrics for a REX talk are accurate and auditable by cross-referencing repository history with the Stage 1 summary and CHANGELOG.

Core Features & Use Cases

  • Cross-reference Stage 1 summary with git history to validate reported metrics.
  • Generate a verified, month-by-month timeline of commits and releases.
  • Produce three output documents ready for presentation and peer review.

Quick Start

Run the research workflow on the target repository to generate the three output files: git-archaeology.md, changelog-analysis.md, and timeline.md.

Frequently Asked Questions about talk-stage2-research

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

FAQPage Schema
How do I verify git commit history metrics for a research presentation?

To verify git commit history metrics, you can cross-reference a Stage 1 summary with repository history using read-only git commands. This extracts commits, authors, and releases to produce an auditable timeline for your research presentation.

How do I generate a verified timeline of git commits and releases?

You can generate a verified timeline of git commits by applying read-only git commands to extract repository velocity and aligning them with the CHANGELOG. This produces a factual timeline document ready for peer review.

Can I cross-reference a git CHANGELOG with repository history for an auditable timeline?

Yes, you can cross-reference a git CHANGELOG with repository history to validate reported metrics. Aligning commits, authors, and releases with the CHANGELOG produces an auditable timeline document ready for presentation.

What is the best way to extract git archaeology data for a REX talk?

The best way to extract git archaeology data is by running a research workflow that applies read-only git commands to the target repository. This generates git-archaeology and changelog-analysis files for your REX talk.

Does this git timeline verification process modify my repository history?

No, the git timeline verification process applies only read-only git commands to extract commits, authors, and releases. It safely cross-references repository history without modifying your existing codebase or git history.

What output files do I get when cross-referencing git history for research verification?

When cross-referencing git history for research verification, you get three output files: git-archaeology.md, changelog-analysis.md, and timeline.md. These files contain the auditable results ready for presentation and peer review.