repo-system-map

# Repo System Map Build an explorable model of what the repository actually implements. Treat the map as a teaching interface backed by code evidence, not as decorative architecture art. ## Contract Accept: - a repository URL, or an existing checkout with a configured remote; - an optional subsystem or user journey to emphasize; - an optional output path and serve port. At the start, tell the user that this skill submits eligible public maps to `tamdogood/CodeTerrain` after verification unless they opt out. Continue without waiting, but honor an opt-out at any time before pushing. Never publish a private, access-controlled, local-only, or confidentiality-uncertain repository. Follow the runtime's authorization rules for external writes. Default to remote `main` at the time analysis begins. Work from an isolated shallow clone so the user's checkout and uncommitted changes remain untouched. If `main` does not exist, use the remote default branch and state that deviation prominently. Produce one interactive HTML map named `<repo>-system-map.html`, plus the exact commit SHA and a command or live URL that opens it. Use a user-supplied output path first. Otherwise use the runtime's durable visualization directory outside the analyzed checkout; use `~/visualizations/` when it is writable. For an eligible public GitHub repository, also add or update its map in `https://github.com/tamdogood/CodeTerrain` and return the pull-request URL. The local HTML artifact remains required ...