From odin
Surfaces a map of surrounding modules, callers, and invariants when you need architectural context before making changes. Uses fd, git grep, and ast-grep for structural orientation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/odin:zoom-outThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Stop reading the local fragment. Climb one level of abstraction and produce a map: which modules surround this region, who calls into it, what it calls out to, and where its invariants live. Dispatch an Explore agent (`fd`-first discovery, then `git grep`/`ast-grep` for call-site enumeration) rather than reading individual files — the goal is structural orientation, not line-level detail.
Stop reading the local fragment. Climb one level of abstraction and produce a map: which modules surround this region, who calls into it, what it calls out to, and where its invariants live. Dispatch an Explore agent (fd-first discovery, then git grep/ast-grep for call-site enumeration) rather than reading individual files — the goal is structural orientation, not line-level detail.
Output is a compact module-and-caller map, not a narrative. Name the surrounding components, the inbound and outbound edges, and any obvious invariant boundaries (transactional scope, ownership, IO surfaces). Stop at one layer up unless the user asks for more — over-zoom dilutes the orientation.
npx claudepluginhub outlinedriven/odin-claude-plugin --plugin odinZooms out to show broader context and a map of relevant modules and callers using the project's domain glossary. Use when unfamiliar with a code section.
Maps the broader context of unfamiliar code areas by listing relevant modules and callers using the project's domain glossary.
Maps module structure and callers when navigating unfamiliar codebases. Use before editing new modules or when asked for a big picture overview.