summarizelisted

# Summarize Skill ## Overview Analyze an entire codebase and produce two artifacts targeted at new developers: 1. **CODEBASE_ARCHITECTURE.md** — a detailed, Obsidian-ready architecture document covering structure, dependencies, data flow, API layer, configuration, and testing strategy. 2. **QUICK_REFERENCE.md** — a concise cheat sheet of commands, key files, patterns, and gotchas for day-to-day navigation. Both files are written to the repository root where the user invoked `/summarize`. --- ## Instructions ### Phase 1 — Parallel Codebase Analysis Use the Workflow tool to fan out **nine parallel analysis agents**. Each agent focuses on a single concern. Launch all nine simultaneously; do not wait for one before starting the next. Assign each agent the following scopes: #### Agent 1 — File Structure & Entry Points - Map the top-level directory tree (depth ≤ 4). - Identify primary entry points: `main.*`, `index.*`, `app.*`, `server.*`, `cmd/`, `src/`. - Note any monorepo layout (`packages/`, `apps/`, `libs/`, `services/`, workspace files). - Record build output directories (`dist/`, `build/`, `out/`, `.next/`, `target/`). #### Agent 2 — Packages & Dependencies - Parse all dependency manifests present in the repo: - JavaScript/TypeScript: `package.json`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml` - Python: `requirements.txt`, `pyproject.toml`, `Pipfile`, `setup.py`, `setup.cfg` - Rust: `Cargo.toml`, `Cargo.lock` - Go: `go.mod`, `go.sum` - Ruby: