resync-map
/resync-map
Resync Ork's interaction map (docs/interaction-map) with the code — review what changed since the last sync, flip statuses that are now built, update facts, doc links, new components and journeys, record the synced commit, validate, and look at it. Use when asked to resync, update or refresh the interaction map, or after a milestone lands.
- Author
- mimshins ↗
- Repository
- ork ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Resync Ork's interaction map (docs/interaction-map) with the code — review what changed since the last sync, flip statuses that are now built, update facts, doc links, new components and journeys, record the synced commit, validate, and look at it. Use when asked to resync, update or refresh the interaction map, or after a milestone lands.
Original author description
Resync Ork's interaction map (docs/interaction-map) with the code — review what changed since the last sync, flip statuses that are now built, update facts, doc links, new components and journeys, record the synced commit, validate, and look at it. Use when asked to resync, update or refresh the interaction map, or after a milestone lands.
How it works
- Procedure
- Report
SKILL.md preview
--- name: resync-map description: Resync Ork's interaction map (docs/interaction-map) with the code — review what changed since the last sync, flip statuses that are now built, update facts, doc links, new components and journeys, record the synced commit, validate, and look at it. Use when asked to resync, update or refresh the interaction map, or after a milestone lands. --- # Resync the interaction map You are bringing every map in `docs/interaction-map/public/js/data/` up to date with the code in this repository. Read `docs/interaction-map/sync.md` and `docs/interaction-map/content-style.md` first; follow `sync.md` step by step. Arguments (optional): a map id to limit the sync to (`architecture`, `lifecycle`, `context`, `messaging`, `feedback`). ## Procedure 1. **Baseline.** Run `pnpm map:check` and keep its output: the commits since the sync, the uncommitted changes, and "Review these statuses" are your worklist. If nothing changed, say so and stop. 2. **Triage.** Group the changes by the map they touch, using the table in `sync.md` §2. Skip dependency bumps and tooling chores that change nothing a map shows. 3. **Review each change against the code**, not the commit message: read the diff, the code and its tests. `built` means on `main` with tests; a field the schema accepts but nothing reads is `partial`; a design section alone is `specified`. 4. **Update the data** (`nodes.js`, `edges.js`, `journeys.js`): statuses on nodes, their edges and journey steps; summaries and facts; doc links to the code and tests; `src` paths; new nodes on the zone grid with their edges and steps; `see` links both ways. Keep cards on the grid described in `design-language.md#layout`, and subtitles within ~30 characters. Never put secrets in the data. 5. **Record the sync** in `public/js/data/sources.js`: `synced` = the short hash you reviewed; `SYNCED_ON` = today (YYYY-MM-DD). 6. **Validate.** `pnpm map:check` must end with `✓ Data and links are consistent.` Then `pnpm map` and, if a browser tool is available, open each touched map: fit (`0`), select a few changed cards, play a changed journey, toggle dark (`T`), and check the console has no errors. Fix overlaps, edges that cross cards, and cut-off subtitles. 7. **Update docs** if the procedure, the maps or the data model changed (`maps.md`, `README.md`, `AGENTS.md`). 8. **Commit** only if the user asked for one: `Sync the interaction map to <sha>`, with a body listing per map what changed. ## Report End with a short summary: the commit range reviewed, per map what changed (status flips, new components and journeys), anything ambiguous you decided, and anything you could not verify.
Versions
The database has no other skills named resync-map.
Database snapshot: 13.11.2026 · package version f6c7fa336233 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100site-map
Builds and verifies the site map of the app, its surfaces, transitions, guards and journeys, through the sitemap verbs in order, and re-checks a stored map against the code. Use when the workflow is site-map or site-map-retest. - 100workspace-map
Build, resync, or repair a shared index of Confluence pages and Miro frames on a Confluence page with a local cache. Use when the user asks to build, bootstrap, refresh, resync, or fix the workspace/diagram map, asks where a page or frame is, or another skill finds the map… - 100update-codebase-map
Refresh an existing .claude/.codebase-info/ map after code changes. Use for stale codebase or architecture docs; use map-codebase to create one. - 100update-project-docs
Brings task.md, changelog.md, and files.md back in sync with what the code says shipped, then prints a commit message as plain text. Reads git history and the working tree, never memory, and refuses to log features it cannot see in source. Use when a feature or fix lands, when… - 90todos-update
Use when user asks to update todos, resync the task list, say what to do next, or plan and tree have drifted apart. Not for coarse lists: use todos-enhance. Not for adding requirements: use todo-add. - 100reseed-architecture
Resync every teaching surface with dev/docs/ARCHITECTURE.md after rulings land in the record: CLAUDE.md, .claude/rules/*, .claude/skills/*, dev/docs/best_practices/*, and the dev docs. The record is the single source of truth; this skill walks the surfaces that teach from it and…