pr-lens
The fastest way to understand code
Runssource: GitHubhomepageTypeScriptMITcommit 1b597ef8ad75
TypeScript, MIT licensed. The project labels itself: agent skills, architecture as code, architecture diagrams, claude skills, code visualisation, codex, coding agents and data flow diagram.
pr-lens runs. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PR Lens monorepo installs, builds, typechecks, and all 868 tests pass on 7 packages (schema, renderer, cli, action, agent-skill, gitlab-component, bitbucket-pipe) with the CLI binary functional at version 0.11.0.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- System Node is v18.19.1 but project requires >=20.111 minute
- pnpm not installed on system1 minute
- Flaky test slug.test.ts timed out in parallel run
- Install time
- 3 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm verify (build + typecheck + test) passed for all 7 workspace packages: 868 tests across 48 test files all passing. CLI binary reports version 0.11.0 and shows full help output.
- Model tokens used
- 143,238
- Exact commit tested
- 1b597ef8ad75
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
✓ test/slug.test.ts > never emits a separator, a reserved name, or anything but a plain segment 59…
✓ test/slug.test.ts > a title that is a device name on Windows still gets a directory 1ms
Test Files 1 passed (1)
Tests 10 passed (10)
Start at 16:26:18
Duration 914ms (transform 57ms, setup 0ms, import 79ms, tests 600ms, environment 0ms)
All 10 slug tests pass (including the one that timed out before, at just 592ms). The timeout was si…
Now I have all the data I need. Let me compose the final result.
tokens used
143,238
All 10 slug tests pass (including the one that timed out before, at just 592ms). The timeout was si…
Now I have all the data I need. Let me compose the final result.Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 3 minutes to install, slower than the median of the 126 comparable projects Argusic has measured.
Of the 127 agent-skills projects Argusic has installed and timed, pr-lens was the 70th fastest to reach a running state, and 95 of 127 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 3 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-skillsarchitecture-as-codearchitecture-diagramsclaude-skillscode-visualisationcodexcoding-agentsdata-flow-diagramdiagrams-as-codemermaid-alternativeopencodesequence-diagramssoftware-architecture-and-designsystem-designtext-to-diagram
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pr-lens)Questions
- Does pr-lens run?
- Yes. pr-lens runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test pr-lens?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1b597ef8ad75. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test pr-lens?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pr-lens take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does pr-lens need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pr-lens?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does pr-lens compare with the alternatives?
- Of the 127 agent-skills projects Argusic has installed and timed, pr-lens was the 70th fastest to reach a running state, and 95 of 127 reached one at all.
- Where is the evidence for pr-lens?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.