explainmyrepo plugin

explainmyrepo turns a GitHub repository into an explainer page and a knowledge pack an agent answers from.

  • 68 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • It reads a repository and sends fragments to external models and an image service.
  • It uses paid keys and can publish a page and a repository on external hosting.
All reasons and checks

stuinfla/repo-explainer

Install

Manual install

npx explainmyrepo https://github.com/owner/repo

The first Get started command from the README; substitute the repository to explain. The Claude Code plugin adds the `/explainmyrepo` command.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • It reads a repository and sends fragments to external models and an image service.
  • It uses paid keys and can publish a page and a repository on external hosting.

This is third-party code. Review the repository files before installing.

What it does

explainmyrepo reads a repository from its link and builds three results: a live explainer page with architecture and data-flow diagrams, a repository that holds the page, and a knowledge pack for an agent. The author runs each page through a quality check on a mobile and a desktop screen and ships it only when the scores clear the bar. The knowledge pack contains a vector knowledge base of the project, a search CLI and an MCP server. Claude Code or Cursor with this pack answer from the real code instead of guessing. It works as a Claude Code plugin with the `/explainmyrepo` command, as an `npx` tool and as a website for public repositories.

Who it is for. Open source maintainers whose README does not explain the idea on the first screen, and anyone who wants an agent to understand an unfamiliar codebase.

Good fit when

  • An open project is going public and needs a page a stranger can follow.
  • An agent gets lost in a large repository and needs an index with symbols and a dependency graph.
  • A review of someone else's repository must be shown to a team or client.
  • A private repository must be explained on your own keys through `gh auth login`.

Not a fit when

  • The repository is small and a plain README is enough.
  • Sources must not go to external models and an image service.
  • You want a quick run without OpenAI keys and ImageMagick.

Example request

Explain https://github.com/owner/repo with a newcomer-friendly page and build a knowledge pack for Claude Code.

Limitations

You need a text-model key or a Claude Code login, an `OPENAI_API_KEY` for imagery and grading, and ImageMagick. A Netlify token is needed for a live link, and without it the page stays local. Runs use paid APIs, so the cost depends on the chosen models. Private repositories require `gh auth login`. A build takes tens of minutes, and the refine loop repeats until the scores pass the bar.

How to disable. Remove the plugin through `/plugin` and clear the generated pages, repositories and keys in `.env`. The explainer repository on GitHub and the hosted page stay with you; delete them separately.

FAQ

What does a run need?

A text-model key or a Claude Code login, `OPENAI_API_KEY` for imagery and ImageMagick on `PATH`. The tool checks all of it before starting and reports what is missing.

Can I skip the keys?

For public repositories the explainmyrepo.isovision.ai website works with no setup. Private repositories and your own accounts go through `npx` and `gh auth login`.

What is inside the knowledge pack?

A vector base of the project, a search CLI and an MCP server. An agent connects the pack and answers from the sources with file references.

How is a weak page kept from shipping?

The gate is strict: a mean score of at least 82 and all six operator questions answered yes. A page below the floor does not reach deploy.

How do I avoid a paid text model?

The same skill runs in a Codex session signed in with a ChatGPT subscription: text costs no tokens and only imagery stays metered.

Discussion

No questions or reviews yet.

Plugins

The CLI builds wikis from local or GitHub codebases, links modules and traces answers to source-file line ranges.

CLIExtended access306Repository stars

Claude Code Docs

Claude Code Documentation Tool

A Claude Code plugin that keeps the official Claude docs at hand, reading each page live from Anthropic on demand, with no mirror and no MCP server

PluginExtended access58Repository stars

A marketplace of five Claude Code plugins for researchers: literature search, research design, project memory and manuscript work

PluginBroad access651Repository stars

Repo Docs Skills

repo-docs-skills

Living project documentation for agents: guides, concepts and reference from real runs next to the source

SkillExtended access426Repository stars

A self-hosted RAG platform: cited answers over GitHub, Notion, Drive and files, with an MCP mode for Claude Code.

MCP serverExtended access126Repository stars

A plugin for studying research papers: a PDF or arXiv link becomes a summary, study materials, code demos and a web viewer

PluginExtended access358Repository stars

README in short

One Claude Code skill holds all the logic, and the plugin, `npx` and the website run it identically. Each page ends with a question box whose answers link to repository files.

README badge

Report a problem