Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/pr-walkthrough
Generate a single-file HTML walkthrough for a pull request.
Passed 16 of 18 test cases with the skill, and 9 of 18 without it.
and 8 more in the full report
8 fixed8 passed either way1 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We made a bug fix to the layout logic in `references/build.py`. What command should we run to verify that the renderer unit tests still pass?
| Checked | Without skill | With skill |
|---|---|---|
| Runs python3 -m unittest test_build inside references/. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate one HTML file that explains why a PR exists and what changes for its users. Lead with the problem, outcome, and compatibility impact. Follow with architecture, code, and trade-offs.
This skill is not a code-review skill. Do not produce review findings, approve/request-changes verdicts, or a full critique. Explain the change so a reviewer understands it fast.
A trusted managed runner supplies a filesystem contract, renders the result, and publishes the HTML. The runner prepares bounded files from the immutable PR head before the agent starts. The agent consumes these files instead of running arbitrary Git or shell commands. The skill never uploads files, changes a pull request, or handles hosting credentials.
You do not write HTML. You write one JSON data file per PR, then run a renderer that builds the HTML:
<output-dir>/pr-<number>.json<output-dir>/pr-<number>.html<output-dir> is the directory for walkthrough files. The default is docs/pr-walkthrough/. The caller may set a different directory. If the host or a CI job gives you an exact path in your instruction, use that path and do not change it. Otherwise use the default and create it if it is missing. <skill-dir> is the directory this skill lives in; use it for the references/ paths in the commands below.
For example, PR #12407 writes pr-12407.json, and the renderer writes pr-12407.html. Never write to a shared index.html, and never overwrite a walkthrough for a different PR. This keeps earlier walkthroughs on disk so several can be opened and compared at once. If a file for the same PR already exists, ask the user before overwriting it.
The renderer is references/build.py (Python standard library only). It reads your JSON and the fixed shell at references/shell.html, then writes the HTML page. The shell holds all CSS and JS and stays the same for every PR. Do not edit shell.html or build.py. The renderer owns the parts that are easy to get wrong: it escapes all code, builds both the canvas and the list from one data source, places the canvas nodes, computes the GitHub file links, and fails loudly on a missing field.
The renderer does not judge whether the content is true, clear, or useful. That is your job, and it is the whole job. A page that passes the build but has a vague tldr, a wrong sig, or a diagram that does not match the code is a failed walkthrough. Spend your effort on the quality of each JSON section, not on the mechanics the renderer already handles. Each section below states the bar it must meet.
See references/example.json for a complete, working data file. Copy its shape.
Read impact.md before collecting evidence or writing the impact sections.
Read feature-flags.md to assess rollout coverage and UX with flags off.
When a trusted managed runner provides an exact draft path and renderer command, write the complete walkthrough JSON object to that draft path. Do not write HTML or change source files. Use the exact path and command from the contract. Do not use alternate paths, command arguments, or JSON on standard input.
If the renderer rejects the draft, repair the reported field or JSON position
test cases passed, vs 9 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.