explainmyrepo

↑ a real one — generated end to end from ruvnet/agenticow, no human design pass. Open it live.

---

The problem it solves

Most repositories are opaque. Open one cold and you can't quickly tell what it is, why it matters, how it's built, or how to use it. The README is usually a wall of text written by someone who already knows the answer — so it assumes you do too.

That hurts twice over now:

• A human lands on your repo, doesn't get it in thirty seconds, and leaves.
• An AI (Claude Code, Cursor) is asked about your repo and guesses, because it has no grounded understanding of the actual source.

A longer README doesn't fix opacity. The goal is bigger than documentation:

Take someone from "I've never seen this before" to "Oh, I get why this was created, the problem it solves, what it does, why it's elegant, how it works — and I'm ready to go implement it."

That's the bar. explainmyrepo exists to clear it, on every build.

---

What you get — three artifacts from one command

One command reads a repo and produces three things, each quality-gated:

1. A live explainer web page — the link you share. A bespoke, art-directed walkthrough with a real architecture diagram and a real data-flow diagram drawn from the code itself.
2. A GitHub repo you own — you're invited as a collaborator on the explainer's own repo, so you can edit it. It's yours.
3. A downloadable AI knowledge pack — a drop-in .zip containing a vector knowledge base of the repo, a search CLI, and an MCP server, so Claude Code or Cursor answer from the real source instead of guessing.

---

How it works — the process

explainmyrepo is not a template filler and not a doc scraper. It's a single Claude Code skill that holds the judgment (the brain) plus small, pure tools that do the mechanics — with one data contract flowing between them. No brittle multi-phase pipeline.

The brain runs the repo through an ordered sequence. Each step has one job: