grimoire-map
Make repository behavior paths navigable through source-backed observations, not an invented architecture. Do not modify production code or prescribe a redesign; a map is not proof of behavior.
Query or build
For ordinary code-navigation questions, inspect only what is needed and return source-backed locations, relationships, and uncertainty. Do not create, refresh, repair, or clean map files; an existing map may be read as a navigation aid, but verify relevant claims against current source. Stop when the question is answered; the map-building procedure below is not a prerequisite.
Persist .grimoire/map/index.json and supporting shards only when the user explicitly requests creating or updating a map, within that scope and any write restrictions. Under orchestration, the caller must pass through that authorization; calling this skill or supplying an artifact path alone does not grant it. If persistence is not authorized, return results inline, not files.
For map-building and cross-skill handoffs, own navigation, source snapshots, inventory/inspection coverage, source dependency edges, and evidence—not improvement findings or acceptance. For cross-skill handoffs, read the shared coordination contract v1.
Inventory and inspect
Record repository identity, revision/dirty state, scope, exclusions, languages, and build systems. Match inventory and inspection to the request; use the whole first-party repository only for a repository-wide map or refactor. Include relevant untracked files, manifests, tests, configuration, and scripts; distinguish generated/vendor content.
- Function: inspect the function and necessary callers, contracts, and tests.
- Module: inspect its internals and adjacent dependencies/consumers.
- Subsystem: fully scan the specified subsystem and inspect its external seams.
- Deep whole-repository refactor: cover every first-party module and cross-module seam.