Maintain Code Map
Map the repo. Lock the evidence.
Builds JSON, Markdown, HTML, and a freshness lock. Unproven edges stay unknown.
Example maps
Four fictional infrastructures.
These PNGs ship in the skill repo as example output, not product UI.
-
checkout-api -
event-ingest -
desktop-studio -
edge-platform
Load
Add the named skill.
Trigger maintain-code-map
npx skills add gvastethecreator/code-map-skill --skill maintain-code-map
Python 3.11 or newer is required on the machine that builds the map.
Install
The README install line.
npx skills add gvastethecreator/code-map-skill --skill maintain-code-map
Commands
Tool entry points.
| Input | Action |
|---|---|
| status | Compare the lock to the tree |
| build | Write JSON |
| validate | Check the staged artifacts |
| publish | Move staging into docs/codemap |
Evidence
What a published map must contain.
-
docs/codemap/codemap.json Nodes and edges with source paths.
-
docs/codemap/codemap.lock Freshness fingerprints.
- Example HTML A browsable map from the four fixtures.
Limits
Do not invent architecture.
-
Unknown edges
Relationships without source evidence stay unknown.
-
Product code
The skill must not edit product files while it builds the map.
Links
Open the skill.
Evidence first. Unknown stays unknown.
Open the repository