repo-activity-summary

# Repo Activity Summary Answer "what's been happening in this repo" from local git history — no network, no tokens, no setup. ## Trigger conditions Use this skill when the user asks: - "What has this repo been working on recently?" - "What technologies does this project use?" - "Where are the high-churn files / hotspots?" - "Who's contributing and what are they working on?" - "Is this project actively maintained?" - Before onboarding onto an unfamiliar codebase. Do not use this skill for file-level blame or provenance — use `investigating-repository-history` for that. ## Quick start ```bash python3 scripts/activity_summary.py --repo-dir . --days 90 ``` | Flag | Default | Description | |------|---------|-------------| | `--repo-dir` | `.` | Path to the git repository | | `--days` | `90` | Days of history to analyze | | `--author` | *(all)* | Filter to one author | | `--format` | `markdown` | `markdown`, `json`, or `text` | | `--max-commits` | `500` | Cap for very active repos | | `--branch` | *(current)* | Branch / revision to analyze (must not start with `-`) | | `--output` / `-o` | *(stdout)* | Write the report to a file (UTF-8) | | `--classify-threshold` | `0.25` | If the share of unclassified commits exceeds this fraction, mark work-type classification unreliable and emit subject samples | | `--max-unclassified-samples` | `40` | Cap on unclassified commit subjects included in the report | | `--raw-subjects` | *off* | Emit every filtered commit subject with sha and ...