commit-archaeologylisted

# Commit Archaeology Thoroughly review the commit history of a specified application for recurring patterns: changes introduced, reverted, and reintroduced; flip-flops in logic or implementation; repeated refactors; and other signs of indecision or systemic rework. ## Usage ``` commit-archaeology <app> [--since <date>] [--path <path>] ``` - **app-name** _(required)_: Application name from `<applications-root>/AGENTS.md` - **--since** _(optional)_: How far back to look (default: `6 months ago`). Accepts any `git log --since` format. - **--path** _(optional)_: Limit analysis to a specific subdirectory or file (e.g., `backend/src/routes`, `frontend/src/pages/dashboard`) ## Instructions ### Phase 1: Gather History 1. **Resolve the app directory** from the app name using the registry in `<applications-root>/AGENTS.md`. 2. **Collect the full commit log** for the time range: ```bash cd {APP_DIR} git log --since="{SINCE}" --format="%H %ad %s" --date=short -- {PATH} ``` 3. **Collect commit diffs** for pattern detection. For each commit in the range, capture the stat and patch: ```bash git log --since="{SINCE}" --stat --patch --reverse -- {PATH} ``` For large histories (500+ commits), break this into batches of ~50 commits to avoid context overflow. 4. **Collect revert commits** explicitly: ```bash git log --since="{SINCE}" --grep="[Rr]evert" --format="%H %ad %s" --date=short -- {PATH} ``` 5. **Collect files with high churn** (