cartographer

Solid

Own the repo map — configure mapping to THIS repo, wire auto-remap, install semantic extractors, curate authored navigation, and finish through one truthful finalization gate. Cartographer-only.

AI & Automation 28 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
49
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 Working shells consume the `dr_*` catalogue and NEVER map. Own its config, automation, semantic extractors, sections, descriptions, shape notices, and completion evidence. Map data = `.sc-state/local/map/map.db`, separate from engine memory. Use: - `sc map-schema [dr_table]` for structure. Pass = the expected `dr_*` object + columns are listed; never guess schema or inspect raw SQLite. - `sc map-sql "…"` for read-only data queries. - `sc map-sql-rw "…"` only for the authored `dr_section` / `dr_filepath.desc` writes named below. - `sc map` to refresh derived rows. - `sc map finalize` to prove completion. Exit `0` = every required row is `PASS` / `N/A`; exit `2` names pending owner actions; exit `1` names a failed check. ## First boot / heal Run this sequence on first boot, after a shape notice, or when the map drifts: 1. `sc map-schema` then `sc map-schema dr_repo`. Pass = map structure is inspectable through the supported surface. 2. Inspect live data: ```sql SELECT name, root, default_branch, file_count, mapped_at FROM dr_repo; SELECT lang, COUNT(*) n FROM dr_filepath WHERE lang IS NOT NULL GROUP BY lang ORDER BY n DESC; SELECT role, COUNT(*) n FROM dr_filepath GROUP BY role ORDER BY n DESC; ``` 3. Tune `.sc-state/local/map/config.json` in the assigned worktree only where defaults are wrong. Config is per-clone runtime state and never a commit. All keys are optional; skip sets extend defaults and ca...

Details

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

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

wayfinder-cartographer

Build a walkable map of a body of work (a repo, a database/base, a vault, a client-delivery folder, an automation pack) that a newcomer or a cold AI can enter and wander without reading the whole thing. Produces a catalog plus one card per noun, marks live/leftover/ghost, and names what each change hits and the wrong neighbour it does not. Use when the user says "map this system/repo/base/folder", "make a map", "onboard someone to X", "what are the moving parts of X", "help a new person or model understand this", or hands over a large body of work someone will change. NOT for diagnosing why something failed, and never map the methodology itself.

1 Updated 1 weeks ago
jdvanleenen-sys
Data & Documents Listed

cartographer

Compile survey records into a map — an append-only body of claims plus a mutable, authoritative index that resolves a topic to the current claim, tracks resolution per area, and marks contested findings. Use when survey records need turning into a map, when a map's index needs bringing current, when findings have accumulated and nobody can tell which are still true, or when a long document has begun superseding itself.

0 Updated 2 weeks ago
dsvid
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.

9 Updated 3 days ago
duthaho