⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
eli5
WHAT: Explains a codebase, a folder, a feature, a command or a pull request to someone who knows nothing about it, as a PR Lens canvas whose walkthrough builds the picture one part at a time. WHEN: /eli5 <thing>, or asked to explain code simply, for a beginner, a new hire, a non-engineer, or 'like I'm five'. KEYWORDS: eli5, explain like I'm five, explain simply, beginner, onboarding, walkthrough, diagram, PR Lens
// RATINGS
// README
Features
Architecture blast radius
What the pull request touches, drawn against the system around it: the components involved, and the calls that run between them.
Colour carries the delta: green new, amber changed, red gone
Data flow you can watch
The ordered pipeline of the change as an animated sequence: one dot crosses one arrow at a time, in the order the steps happen.
See the payload on every data flow
Click any arrow and the payload opens beside the graph: request and response, each as a declared shape or a sample body. New keys land green, dropped ones red, the same colours the graph uses.
Drill down without leaving the page
The comment nests <details> sections, each carrying its own diagram scoped to one part of the change: the whole blast radius on top, then the new path, then what was retired.
Open it big
Every comment links to the interactive canvas: the same diagrams at full size, with pan, zoom and a light or dark theme, so a large change is read at the size it needs rather than the width of a comment.
Walk the change
A walkthrough tours the change one step at a time. It dims everything else, lights the cards and routes for that step, and says in a line what happened there. Press play on the canvas, or W.
Your agent, live on the canvas
Ask your local coding agent to connect live to a canvas, then use it to understand any codebase or code change. Ask follow-up questions, drill into any part of the graph, or drag across several nodes and ask your agent about them.
From one card to a monorepo
The same visual grammar answers for every size of change: lanes, node cards, delta colours, and routes you can trace with your eye alone.
For what its worth, you should not be opening a PR this large
Light or dark theme
With the Github app, every diagram ships as a pair, and GitHub shows the one that matches the reader's theme. Or you can render any theme locally via your coding agent
Hall of Fame
The pull requests behind Hooks, Node fetch and Ingress, run back through PR Lens. Same renderer and same contract as the diagrams above.
<a href="https://prlens.dev
// HOW IT'S BUILT
KEY FILES