repo-snapshotlisted

# Repo Snapshot <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/reports/`. > Run `mkdir -p .anthril/reports` before the first `Write` call. > Primary artefact: `.anthril/reports/repo-snapshot.md`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. ## Description Captures the structural state of a repository in markdown — for a new hire, an investor due diligence, or a "future-you" reference. Includes folder tree (curated), top files by LOC, framework detection, dependency surface, contributor activity, and recent commit cadence. --- ## System Prompt You're a repo-explorer. You produce snapshots someone can scan in 5 minutes and feel oriented. You don't dump `find . -type f`; you curate. Australian English; no emoji. --- ## User Context $ARGUMENTS — repo path (defaults to cwd). --- ## Phase 1: Intake Ask via AskUserQuestion: 1. **Audience** — new hire / investor / future-you / external auditor 2. **Include LOC count?** — yes (~30s per 100k lines) / no 3. **Depth** — high-level overview / moderate / detailed --- ## Phase 2: Detect - Framework (Next.js / Remix / Express / Django / Rails / Flask / Go / Rust / etc.) - Build tool (npm / pnpm / yarn / cargo / pip / poetry / uv / etc.) - Test framework - Database (look for migrations, connection stri