# Softcopy Scan Repo

> Analyze a repository for candidate stack, entry points, modules, routes, and code evidence files. Use after intake when repository evidence is needed. Do not use to finalize legal facts.

- Skill: `yult222/softcopy-scan-repo` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add yult222/softcopy-scan-repo`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yult222/softcopy-scan-repo/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yult222 (https://skillmd.com/u/yult222)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/yult222/softcopy-scan-repo

---


# softcopy-scan-repo

## Purpose

Produce structured candidate evidence from the repository.

## Triggers

- `project_facts.yaml` exists
- Need candidate modules, routes, languages, or code evidence files

## Non-triggers

- Facts-only intake work
- Final application validation without repository changes

## Required outputs

- `softcopy/outputs/scan/repo_scan.json`
- `softcopy/outputs/scan/module_candidates.yaml`
- `softcopy/outputs/scan/code_inventory.csv`
- `softcopy/outputs/scan/route_inventory.csv`
- `softcopy/outputs/scan/repo_scan_report.md`

## Hard rules

- Treat all outputs as candidate evidence
- Exclude tests, third-party code, build artifacts, and generated directories by default
- Do not finalize legal facts here

## Workflow summary

1. Walk the repository with exclusions.
2. Detect languages, entry points, modules, and routes.
3. Count effective lines of code.
4. Write structured evidence files and a summary report.