PR Lens by Coldtea

Read the system change before the individual lines

PR Lens is designed to answer questions such as which component now calls a service and where data moves after a refactor. New, modified, and removed elements use different visual treatments. The view keeps relevant surrounding components so the change can be understood in context.

For example, a change that moves email delivery into a queue is easier to discuss as API → queue → worker. That example illustrates the kind of relationship to inspect, not a diagram that every PR will produce.

Try a diagram on a real pull request

1. Choose a PR with a clear change across a few files and use the official GitHub App or skill.
2. Generate the architecture or data-flow view for that change.
3. Open the canvas and follow the modified components and their connections.
4. Compare the important edges with the source, correct misleading labels through repository configuration, and continue the code review.

The documented skill installation command is:

npx skills add coldteadotai/pr-lens

Use the diagram to guide questions

Ask what happens on failure, which caller still uses the old path, and whether the tests exercise the new boundary. Those questions turn a visual overview into a review aid. A polished diagram is a model of the code, not proof that the code behaves correctly.