pr-stacker SKILL.md skillA
pr-stacker from pantheon-org/tekhne is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pantheon-org/tekhne/pr-stacker@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
- pantheon-org/tekhne
- Path
skills/project-mgmt/planning-toolkit/pr-stacker/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Sep 23, 2026
- First version recorded
- Apr 6, 2026
- Size
- 6,112 bytes
- Repository stars
- 10
- License
- MIT
Splits a large feature branch into smaller, focused pull requests using stacked branches and cherry-pick. Groups commits by concern (infrastructure, application logic, tests, housekeeping), proposes descriptive branch names for user approval, creates stacked branches, and generates What/Why MR titles and descriptions. Use when the user says a PR is too big, asks to split a PR, wants to decompose a branch, or needs to break work into reviewable chunks.
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
# PR Stacker ## Mindset A large PR fails reviewers because it mixes concerns — infrastructure sits next to business logic sits next to test cleanup. Reviewers cannot build a mental model of any single change when everything changes at once. The fix is to group commits by **what kind of thing changed**, not by when they were written or what ticket they belong to. Each group becomes its own PR targeting the previous one (stacked branches), so changes can be reviewed and merged in order without blocking unrelated work. Two failure modes to avoid: 1. **The monolith** — one PR with everything, reviewers give up or rubber-stamp 2. **The over-split** — one PR per commit, stacked 10 deep, merge overhead exceeds the benefit The sweet spot is 2–4 PRs where each one can be understood by a reviewer who only knows that domain. ## When to use - A PR has more than ~15 files changed across unrelated concerns - A reviewer says "this is too big to review" - Commits already have phase or step markers in their messages - Changes span infrastructure, application code, and cleanup in a single branch ## When not to use …
Read the whole file at its exact version.
How to install
mdr add pantheon-org/tekhne/pr-stacker@sha256:a2e53f9cf1c3166eThe 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_frpnulb47qsnka5x)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 6, 2026 and Sep 23, 2026, about one every 170 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-23 | 7852cb4 | 6,112 B | A | view · diff |
| v1.0.0 | 2026-04-06 | 2f91c1b | 5,927 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 (6112 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
pantheon-org/tekhne · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_frpnulb47qsnka5x GET https://markdownregistry.com/api/v1/resolve?ref=pantheon-org/tekhne/pr-stacker GET https://markdownregistry.com/api/v1/blob/a2e53f9cf1c3166e3ba9f264a9fc83215ec8d2cebb1e77d080b1e94be4804f3c
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.