← ClaudeAtlas

rescue-maplisted

Maps an unfamiliar codebase before anyone changes it: languages, entry points, how to build, run and test it, module boundaries, data stores, external services and the environment variables it needs. Writes rescue/map.md with a mermaid module diagram and a "where to start reading" list, every claim tied to a file path. Read-only. Use when the user says "I just inherited this codebase", "map this repo", "where do I even start", "how is this project laid out", "what does this app talk to", "explain the architecture of this legacy app", or "onboard me to this repo".
vivekbhange-hub/legacy-rescue-skill · ★ 0 · Data & Documents · score 75
Install: claude install-skill vivekbhange-hub/legacy-rescue-skill
# rescue-map You are drawing the map before the rescue. Nobody fixes what they cannot find. This skill reads the repository, never runs or changes it, and writes one document a new maintainer can trust: what the system is made of, how to start it, what it depends on, and which twenty files to read first. Every statement in the map points at a file. If you could not confirm something, it goes under "Unknowns", not into the map. ## Inputs - `$ARGUMENTS`: path to the repository or a sub-folder. Default: the current directory. - Optional: anything the user already knows ("it is a Django monolith", "prod runs on ECS"). Treat it as a claim to verify, not a fact. ## Output - `rescue/map.md` in the user's repository (create `rescue/` if needed). - `rescue/inventory.md`, the raw output of the inventory script, kept as evidence. ## Steps 1. **Check the ground.** Run `git status --short | head -20` and `git log -1 --format='%h %ad %an' --date=short`. Note uncommitted changes and the age of the last commit. If the folder is not a git repo, say so; later skills (hotspots) need history. 2. **Take the inventory.** Run: ``` python3 "${CLAUDE_SKILL_DIR}/inventory.py" <path> --output rescue/inventory.md ``` It lists languages, top-level directories with sizes, manifests, CI and container files, declared commands (package.json scripts, Makefile targets, Procfile), likely entry points, environment variables the code reads and keyword hints of data stores and ser