Skip to content

Project Catch-Up

Summarize what landed on main plus quick quality signals. Keep execution deterministic by collecting commit data with the bundled script, then produce the report from that dataset.

1) Gate - Scope Before Git (Mandatory)

Never assume scope. Require one explicit scope before running history commands:

  • Last 3 days
  • Last 10 days
  • Last 30 days
  • Since date YYYY-MM-DD
  • Last N commits

When interactive option tools are available, use them first. Otherwise ask in plain chat and wait for an explicit choice.

2) Collect Facts with Script (Deterministic Path)

Use scripts/collect-history.sh so commit extraction and size stats are captured in one pass.

Examples:

# Last N commits
bash scripts/collect-history.sh --repo . --branch main --count 30

# Date window
bash scripts/collect-history.sh --repo . --branch main --since "10 days ago"

# Specific output file
bash scripts/collect-history.sh --repo . --since "2026-05-01" --output /tmp/project-catchup.tsv

Rules:

  • Do not run this script until scope is confirmed.
  • Pass explicit flags only (--count, --since, or --after).
  • Do not silently substitute defaults.
  • If the script errors, report the error and ask to revise scope.

3) Report Shape (Required)

Return sections in this order:

  1. ### ๐Ÿ‘“ Summary
  2. ### ๐Ÿ“ถ Review signals
  3. ## Per-Commit Detail with the five-column table

Use the detailed scoring/table enums from:

  • references/report-spec.md

Use the sample shape from:

  • examples.md

4) Deep Pass (Optional)

Only include deep-pass artifacts when explicitly requested:

  • file-level blob links
  • author rollup
  • filtered history by author/path/window

5) Output Checklist

  • [ ] Scope explicitly confirmed
  • [ ] Deterministic collector script used for facts
  • [ ] Section order is ๐Ÿ‘“ then ๐Ÿ“ถ then table
  • [ ] Summary threads use the borderless row-list layout (Thread ยท What landed, --- separators, no pipe table)
  • [ ] Review signals use the borderless row-list layout (Signal ยท Notes, all five rows, no pipe table)
  • [ ] Per-commit table uses exactly five required columns
  • [ ] Enum-only values used for Msg vs files and App vs Tests
  • [ ] Deep pass included only on request