← Atlas ScoutCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Atlas Scout
Snapshot Sep 30, 2026 · 23:13 UTC · version 1.0.0-preview.29
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "atlas-scout-code-navigation",
"description": "Use Atlas Scout for local structural code navigation involving definitions, symbols, callers, references, dependency paths, architecture, traces, or edit impact. Use when asked where a symbol is defined, who calls or uses a function, what implements an interface, what breaks if code changes, or how a codebase is organized.",
"included_files": [],
"skill_md_contents": "---\nname: atlas-scout-code-navigation\ndescription: Use Atlas Scout for local structural code navigation involving definitions, symbols, callers, references, dependency paths, architecture, traces, or edit impact. Use when asked where a symbol is defined, who calls or uses a function, what implements an interface, what breaks if code changes, or how a codebase is organized.\n---\n\n# Atlas Scout code navigation\n\nAtlas Scout provides local structural-index evidence for code-navigation tasks. Select a matching\nScout capability when it fits the user's requested evidence:\n\n- For a broad task or unfamiliar subsystem, call compact `fast_context` once for a source/test\n shortlist and exact ranges.\n- `symbol_outline` lists declarations and exact ranges in a known file.\n- `symbol_search` locates definitions and returns stable symbol ids.\n- `symbol_references` returns indexed callers, references, and implementations.\n- Graph, trace, path, architecture, and edit-impact tools return their corresponding bounded\n structural evidence.\n- Omit `detail` and `limit` on initial discovery. Read useful cited ranges before another broad\n navigation call, and stop when the evidence is sufficient.\n\nText search remains useful for literals, regular expressions, generated or malformed code,\nunsupported or partial language coverage, and focused completeness checks. Other development tools\nremain appropriate for builds, tests, package managers, Git, servers, metrics, and runtime\ndiagnostics. Check Scout's coverage and trust metadata before treating an empty result as\nexhaustive, and choose whichever available tool best fits the user's request.\n"
}SHA-256: 166ed2ac96dc278801e41ed4b6efe5270d747ea80c72d1bdf04ec1169fd19e5b