- Home
- Skills
- Code Quality & Review
- PR Walkthrough
PR Walkthrough
Turn a finished branch or PR into a single HTML walkthrough that explains why the change looks the way it does, so a human reviewer understands it before reading the diff.
Free
Works with the AI Agents you already use
PR Walkthrough
Example session with this skill installed
/pr-walkthrough 42
- Read your context and instructions
- Compiled the pr walkthrough
- Generated the UI component
I have analyzed the diff for PR #42 and collected context from the modified files. After our brief interview regarding the architectural tradeoffs, I have generated the walkthrough.
PR-42 Walkthrough: User Authentication Refactor
The generated documentation is now available at docs/review/pr-42.html. It includes the architecture diagram for the new middleware flow, the status pills for the updated service layers, and the reviewer's checklist we discussed.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Walkthrough: User Authentication Refactor</title>
<style>
/* Verbatim styles from walkthrough-example.html */
.story-section { margin-bottom: 2rem; }
.callout.why { border-left: 4px solid #2ecc71; padding: 1rem; background: #f9fff9; }
.pill.warn { background: #f1c40f; color: #000; padding: 2px 6px; border-radius: 4px; }
.diagram { font-family: monospace; white-space: pre; background: #eee; padding: 1rem; }
</style>
</head>
<body>
<nav class="sidebar">
<ul>
<li><a href="#starting-point">Where we were</a></li>
<li><a href="#scope">The shape of the change</a></li>
<li><a href="#auth-flow">Auth Flow Architecture</a></li>
<li><a href="#deferred">Deferred Work</a></li>
</ul>
</nav>
<main>
<section id="starting-point" class="story-section">
<h1>User Authentication Refactor</h1>
<p>The previous implementation relied on a bloated singleton that handled both session persistence and JWT validation.</p>
</section>
<section id="scope" class="story-section">
<h2>Scope Table</h2>
<ul>
<li><code>src/auth/middleware.ts</code> <span class="pill good">Implemented</span></li>
<li><code>src/auth/service.ts</code> <span class="pill warn">Partial</span></li>
</ul>
</section>
<section id="auth-flow" class="story-section">
<h2>Architecture</h2>
<div class="diagram">
[Request] -> [New Middleware] -> [JWT Strategy] -> [User Data]
|
[Session Store]
</div>
<div class="callout why">
<strong>Why:</strong> We separated the strategy from the middleware to allow for future OIDC support without touching the request pipeline.
</div>
</section>
<section id="deferred" class="story-section">
<div class="callout deferred">
<strong>Deferred:</strong> Refresh token rotation was scoped out to meet the sprint deadline; currently using short-lived access tokens only.
</div>
</section>
</main>
</body>
</html>
Next steps
- Open
docs/review/pr-42.htmlin your browser to verify the layout and scroll-spy links. - Review the Reviewer's Checklist section to ensure it covers the specific edge cases for the JWT strategy.
- Attach the link to this HTML file in your GitHub PR comment for the human reviewer.
pr-42.html
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
AI agents write code faster than people can review it. A single feature can arrive as thousands of lines across dozens of files, and the reviewer has to piece together the target behaviour, the key changes, and the tests to run by chasing dependencies through the diff. PR Walkthrough tells the change as a story instead. It reads the branch diff (or a PR via gh) and the most-changed files, asks the author only what the code and commits can't answer, and writes one self-contained HTML file at docs/review/<slug>.html. The page moves from where the code was, through the architecture and each module, to what was deferred, how it was tested, and a reviewer's checklist. Why, Tradeoff, and Deferred callouts record the decisions the diff doesn't show, and status pills mark each file as implemented, partial, or stubbed. Before finishing, it checks that every cited file exists and no pill claims more than the code does.
Requires GitHub CLI for PR mode. Single-file HTML output only (no external images). Large diffs (>5000 lines) will be summarized rather than fully processed.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 14 days ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts
File Scopes
Shell use is read-only: `git diff`, `git log`, `git show`, `git rev-parse`, `git symbolic-ref`, `git status`, and in PR mode `gh pr view` / `gh pr diff`. Runs the bundled `scripts/collect_context.sh`, which only calls those commands. Writes only `docs/review/<slug>.html`. No environment variables or credentials beyond an existing `gh` login.