resume-scanlisted

# resume-scan Intelligent code repository scanner that extracts resume-worthy insights from code structure and git history. Produces structured, accuracy-annotated project summaries ready for resume generation. ## Adaptive Scanning Flow ### Step 0: Author Identity Confirmation Before any analysis, establish the target author identity: 1. **state.json profile** — check `state.json.profile.git_authors[]` for previously confirmed identities 2. **--author param** — explicit author keys passed via CLI (`--author "wei, zhangyaowei"`) 3. **--detect-authors mode** — run `git shortlog -sne` and present top contributors for user selection 4. If no author can be determined, prompt the user interactively before proceeding 5. Store confirmed authors back to `state.json.profile.git_authors[]` for future runs ### Step 1: Quick Probe (All Projects) Run a lightweight probe across every target path to collect surface-level signals: - `ls` root directory structure (top-level layout, monorepo detection) - README.md / README content (project purpose, badges, architecture diagrams) - Dependency files: package.json, go.mod, Cargo.toml, requirements.txt, pom.xml, build.gradle - Config files: Dockerfile, docker-compose, Makefile, CI configs (.github/workflows, .gitlab-ci) - `Glob` file-count stats by extension (*.go, *.ts, *.py, etc.) - AI signal files: CLAUDE.md, .cursorrules, .cursor/, Skills/, MCP configs, agent configs Reference: [scan-strategy.md](references/scan-strategy.md) for the fu