stacked-pr-review-per-base-diff-and-attach SKILL.md skillA
stacked-pr-review-per-base-diff-and-attach from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/stacked-pr-review-per-base-diff-and-attach@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/stacked-pr-review-per-base-diff-and-attach/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed Aug 10, 2026
- First version recorded
- May 29, 2026
- Size
- 9,529 bytes
- Repository stars
- 3
- License
- MIT
Reviewing a stack of dependent pull requests: diff each one against ITS OWN base rather than against main, and attach the reports to the bottom branch.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Stacked PR review: per-base diffs + base-branch attachment ## Problem Reviewing a stack of N dependent PRs (where #B is based on #A, #C is based on #B, etc., rather than each PR being based on main) hits two distinct issues: 1. **Diff capture for reviewer agents.** If you naively run `gh pr diff <N>` against every PR in the stack, gh defaults to comparing against the PR's declared base — which is correct. But if you pre-filter via `git diff main..pr-branch`, you'll include all upstream PRs' changes in the "downstream PR's diff," and reviewers will flag findings against code that actually shipped 2 PRs ago. The reviewer attributes the finding to the wrong PR, and the author of the downstream PR is left confused. 2. **Where to commit the review reports.** Once 3 reviewer agents have produced `reviewer_correctness.md`, `reviewer_architecture.md`, `reviewer_security.md`, they need to live somewhere reachable by every PR in the stack — but committing them to the top-of-stack PR pollutes that PR's diff (the reports become "changes" the topmost PR is making). The base-of-stack PR is the natural home. ## Context / Trigger Conditions …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/stacked-pr-review-per-base-diff-and-attach@sha256:abc74f3932a2ad9dThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_uoiiehhf6xzkjrgz)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 29, 2026 and Aug 10, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-10 | 5b6d8a2 | 9,529 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a58c34c | 9,506 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a39e221 | 10,248 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 9,136 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9529 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uoiiehhf6xzkjrgz GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/stacked-pr-review-per-base-diff-and-attach GET https://markdownregistry.com/api/v1/blob/abc74f3932a2ad9d2ab30a930b278d3c5e90b0159e5078254b727c69fbf8dde2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.