cartographer

Solid

Own the repo map — configure mapping to THIS repo, wire the auto-remap git hooks, heal both on drift. Cartographer-only; no working shell maps. Run on first boot + whenever the map looks wrong.

AI & Automation 15 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
40
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# cartographer — own the repo map so no other shell has to Working shells consume the `dr_*` catalogue (`surface_catalogue`) and never map. You alone do three things: **configure** how this repo is mapped, **wire** the automation that keeps it fresh, **heal** both on drift. Map db = `.sc-state/map.db` in tracked mode or `.sc-state/local/map/map.db` in local mode, separate from the engine memory db (`shell_db.db`) so an engine schema change never touches the map. Reads: `sc map-sql "…"`. Authoring writes (UPDATE/INSERT/DELETE on `dr_*`): `sc map-sql-rw "…"` — `sc map-sql` refuses writes. Authored sections serialize to `.sc-state/map_content.sql` (tracked mode) or `.sc-state/local/map/content.sql` (local mode) on snapshot (admin/GUI step — see Standing jobs) and reload on a fresh map db. `<self>` = your `shell_id` (ACTIVE SESSION block). ## Freshness machinery — what you own - **Git hooks** `post-merge` / `post-checkout` / `post-rewrite` re-run `sc map` on every pull / branch-switch / rebase. Tracked in `.super-coder/hooks/`, fired via `core.hooksPath` — per-clone, unset until `sc map-setup` wires it. - **`sc rebuild`** re-maps (map = derived cache) -> a fresh rebuild never leaves an empty map. - **Hourly cron** — pm2 runs `sc-map-<repo>` on `cron_restart` (`.super-coder/ecosystem.config.cjs`) while the stack is up (`sc up`); catches uncommitted local restructuring the git hooks can't see. Verify: `pm2 list | grep sc-map` — state cycling stopped→online per tick...

Details

Author
jedbjorn
Repository
jedbjorn/subfloor
Created
1 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

SQLite · Database

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

map

Codebase orientation for an unfamiliar or large repo — "map this before I work in it." Fans out read-only Explore sub-agents that navigate the code (keyless — grep/glob/read, no embeddings to go stale) along the order that matters: entry points, build/test/lint commands, architecture and key abstractions, conventions and gotchas, test layout. Distills the findings into a lean AGENTS.md at the repo root — the cross-tool standard file many agents auto-load — where every claim points to a real file and nothing survives that isn't load-bearing. Human-in-the-loop: it drafts, you approve, and it never writes or commits into your repo without an explicit yes. Stamps the map with date + commit so /map refresh regenerates only what went stale. Use before working in a repo you or the agent don't know — e.g. "/map", "/map the auth subsystem", "generate an AGENTS.md", "/map refresh". Run it upstream of feature or bugfix; for the end-of-session shipping gate use done.

6 Updated today
duthaho
AI & Automation Listed

map

Build or refresh the Forge repo map in .forge/map/ — architecture.md, index.md, conventions.md, hotspots.md. Narrative, not call graphs. Salience seeded from objective signals (git churn, reference counts), curated by judgment. Use for /forge:map, when asked where something lives or how the codebase is structured, before exploring any repo that has a .forge/map/, or when the map is stale/missing.

0 Updated yesterday
BenMacDeezy
Code & Development Listed

repo-map

Use when current Git or non-Git workspace truth needs a durable map of roots, ownership, architecture, commands, task routes, and reusable contracts, or an existing map needs evidence-based repair; do not use for ordinary task-local discovery or change review.

2 Updated today
idaibin