← ClaudeAtlas

explore-codelisted

Navigate and understand a codebase using Loom context packets. Find functions, trace call chains, understand architecture — without reading files.
ddevilz/loom · ★ 3 · AI & Automation · score 77
Install: claude install-skill ddevilz/loom
# Explore Code Navigate an indexed codebase using Loom's search and context tools. ## Steps ### 1. Session start Call `start_session(agent_id="claude-code")` — record the returned `session_id` for use at next session start. If you have a previous `session_id`, call `get_delta(previous_session_id=<id>)` first to see what changed since last time. ### 2. Orient to the codebase Call `graph_stats()` — understand the repo shape (how many functions, files, classes, communities). Call `get_work_plan()` — get a prioritized action list (`DOCUMENT` / `INVESTIGATE` / `EXPLORE` / `NOTHING`) based on annotation coverage and graph topology. Call `suggest_questions(limit=5)` — get the graph topology's suggested investigation priorities. ### 3. Find the code the user is asking about Use the user's keyword/question as search input: ``` search_code("<user's keyword>", limit=10) ``` If results have `summary` fields — read them. Skip file reads. ### 4. Get context on the most relevant result ``` get_context("<node_id from step 3>") ``` Returns: summary, signature, callers (top 10), callees (top 10), community, staleness. If `summary_stale: true` — mention to user that source changed and summary may be outdated. ### 5. Trace call chains if needed For "who calls this?" questions: ``` get_context("<node_id>", callees_limit=0) get_blast_radius("<node_id>", depth=2) ``` For "what does this depend on?": ``` get_context("<node_id>", callers_limit=0) ``` For "how does A connect to B?