← ClaudeAtlas

context-maplisted

Generate a map of all files relevant to a task before making changes. Works from a short or vague task description: expands it into concrete search seeds, locates code with rag-rat / codebase-memory / serena, traces dependencies and tests, and outputs a reviewed context map. Use when user says 'context map', 'map the files for this task', 'what files will this change touch', or before any non-trivial change.
Ronnasayd/aipp · ★ 3 · AI & Automation · score 65
Install: claude install-skill Ronnasayd/aipp
# Context Map Before implementing any changes, map the files the task touches. Input may be one vague sentence: expand it into seeds, find **anchors** (code the task most directly changes), then expand outward from them. Every path in the map must be verified; absence of search results is not proof of absence. ## Task $ARGUMENTS This skill runs as an isolated subagent: it has no conversation history and cannot ask the user anything. If the task above is empty, stop and return `status: partial` with `reason: missing task description`. If it names an earlier map, read it and extend it. ## Workflow Tool per question: [tool-selection.md](references/tool-selection.md). Never `cat` whole files — outline first, read excerpts. Run independent searches in parallel. rag-rat, codebase-memory and serena are servers behind mcp-manager: `get_tool_schema(server, tool_name)`, then `call_tool(server, tool_name, arguments)`. Use them first; grep alone misses callers and blast radius. If a server is unavailable, name it under Not Checked. | # | Phase | Action | Gate | | --- | -------------------- | -------