explain-repo

Topics in the source

• explain-repo
• When to load
• How to use
• Gotchas
• References — load on demand

Turns a repository into whichever document a human actually needs from it — not a single format, five purpose-built ones. Reads repo-audit's findings when they exist so the honest parts are already verified, not invented on the spot. CANARY: explain-repo-loaded-2026-09-21-fb78d23e-409ac59f361f8f40 Load this when the ask is for a document about the repo, for a human reader — "explain this", "write it up", "prep me to talk about this", "onboarding doc". Not when the ask is to find problems in the repo (use repo-audit) or to change the repo's own code or docs (use execution or whatever skill owns that file). If a request mixes both — "audit this and then write me an explainer" — run repo-audit first; this skill's whole value is building on verified findings rather than fresh guesses. 1. Get the source material. Look for an existing repo-audit findings JSON first — its findings carry severity and confidence, so the high-confidence ones can be leaned on directly. If none exists, do a light orient-only read (README, root memory file, top-level layout) instead, and say plainly that this document skips the deep verification a full audit would have done. Check: can name what evidence backs

This is an excerpt. Refer to the complete source and its current requirements.