Aidd Review
paralleldrive/aidd
Conduct a thorough code review focusing on code quality, best practices, security, test coverage, and adherence to project standards and functional requirements.
Decide whether planned vertical implementation work should ship as independent pull requests or as a stack of small ordered pull requests, then plan, build, review, update, and merge the stack safely.
Install Stack Pull Requests
$ npx skills add citypaul/.dotfiles --skill stack-pull-requests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install citypaul/.dotfiles stack-pull-requests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/citypaul/.dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/.claude/skills/stack-pull-requests .claude/skills/stack-pull-requests && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "stack-pull-requests" agent skill from https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/stack-pull-requests into .claude/skills/stack-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-pull-requests", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/stack-pull-requestsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add citypaul/.dotfiles --skill stack-pull-requests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install citypaul/.dotfiles stack-pull-requests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/citypaul/.dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/.claude/skills/stack-pull-requests .agents/skills/stack-pull-requests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stack-pull-requests" agent skill from https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/stack-pull-requests into .agents/skills/stack-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-pull-requests", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add citypaul/.dotfiles --skill stack-pull-requests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install citypaul/.dotfiles stack-pull-requests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/citypaul/.dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/.claude/skills/stack-pull-requests .cursor/skills/stack-pull-requests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stack-pull-requests" agent skill from https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/stack-pull-requests into .cursor/skills/stack-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-pull-requests", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/citypaul/.dotfiles.git --path claude/.claude/skills/stack-pull-requests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add citypaul/.dotfiles --skill stack-pull-requests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install citypaul/.dotfiles stack-pull-requests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/citypaul/.dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/.claude/skills/stack-pull-requests .gemini/skills/stack-pull-requests && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stack-pull-requests" agent skill from https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/stack-pull-requests into .gemini/skills/stack-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-pull-requests", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install citypaul/.dotfiles stack-pull-requestsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add citypaul/.dotfiles --skill stack-pull-requests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/citypaul/.dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/.claude/skills/stack-pull-requests .github/skills/stack-pull-requests && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stack-pull-requests" agent skill from https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/stack-pull-requests into .github/skills/stack-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-pull-requests", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add citypaul/.dotfiles --skill stack-pull-requests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install citypaul/.dotfiles stack-pull-requests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/citypaul/.dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/.claude/skills/stack-pull-requests .opencode/skills/stack-pull-requests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stack-pull-requests" agent skill from https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/stack-pull-requests into .opencode/skills/stack-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stack-pull-requests", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
stack-pull-requests- GitHub stars
- 739
- Token cost
- ~6.2k tokens
- SKILL.md length
- 3,141 words
- Files
- 3 (incl. references)
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Decide whether planned vertical implementation work should ship as independent pull requests or as a stack of small ordered pull requests, then plan, build, review, update, and merge the stack safely.
- Works in 5 steps: Fix The Story And Stack Scope → Draw The Lineage Graph → Route Verification By Boundary Type → …
- One slice is too large for effective review
- SKILL.md covers Keep The Three Units Separate, Decide: Independent PRs Or A…, Design The Stack Before… and Write The Delivery Plan, plus 4 more sections
- Calls gh
What it does
Stack Pull Requests is an agent skill from citypaul/.dotfiles. Decide whether planned vertical implementation work should ship as independent pull requests or as a stack of small ordered pull requests, then plan, build, review, update, and merge the stack safely. Use when one slice is too large for effective review, when later slices should proceed on the same evolving baseline before earlier pull requests merge, when AI-generated code volume needs deliberate review boundaries, when a plan already defines dependent pull request boundaries or non-trunk bases, or when the user…
Its SKILL.md is about 6.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/source-notes.md`).
It sits in Development, covering Pull requests and User stories.
When your agent uses it
- One slice is too large for effective review
- Later slices should proceed on the same evolving baseline before earlier pull requests merge
- AI-generated code volume needs deliberate review boundaries
- A plan already defines dependent pull request boundaries
Example prompts
- “/stack-pull-requests”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Fix The Story And Stack Scope
- Draw The Lineage Graph
- Route Verification By Boundary Type
- Verify CI Topology Before Stacking
- Make Intermediate States Safe
What it can do on your machine
Read from SKILL.md and the folder at commit cd4028d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Stack Pull Requests loads about 6.2k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 191 tokens; SKILL.md has 3,141 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,141 words (~6,191 tokens).
“Use stacked pull requests as an optional branch, review, and integration topology, not as a substitute for vertical story splitting.”
- name
- stack-pull-requests
Files
SKILL.md and 2 other files (references) in claude/.claude/skills/stack-pull-requests of citypaul/.dotfiles.
- SKILL.md
- agents/openai.yaml
- references/source-notes.md
Open the folder on GitHubat commit cd4028d
Compare with similar skills
Stack Pull Requests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stack Pull Requests this skillcitypaul/.dotfiles | 739 | — | ~6.2k | Automated safety check: Pass | Custom licence | |
| Aidd Reviewparalleldrive/aidd | 384 | — | ~945 | Automated safety check: Pass | MIT | |
| QAwp-media/wp-rocket | 767 | — | ~552 | Automated safety check: Pass | GPL-2.0 | |
| Acceptance Criteria Checkshopsys/shopsys | 350 | — | ~1k | Automated safety check: Pass | Custom licence | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
QA
wp-media/wp-rocket
Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment.
Acceptance Criteria Check
shopsys/shopsys
Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
More from citypaul/.dotfiles
All 44 skills in this repoFind Skills
citypaul/.dotfiles
Discover and, with authorization, install agent skills from the open skills ecosystem.
Render Code Shape
citypaul/.dotfiles
Render the shape of code — module boundaries, the types that cross them, signatures, and a cited call graph — for code that already exists or a change about to be built.
Structure Codebase
citypaul/.dotfiles
Design, audit, and evolve physical source and package structures that expose real architectural boundaries while keeping related behavior together.
Test Design Reviewer
citypaul/.dotfiles
Review test quality using Dave Farley's eight properties of good tests.
Characterisation Tests
citypaul/.dotfiles
A skill your agent uses when modifying existing code that lacks tests and you need to document its actual current behavior before making changes -- the legacy code dilemma where you need tests to…
CI Debugging
citypaul/.dotfiles
Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis.
Related
Categories
Questions about Stack Pull Requests
What does Stack Pull Requests do?
Decide whether planned vertical implementation work should ship as independent pull requests or as a stack of small ordered pull requests, then plan, build, review, update, and merge the stack safely. dotfiles. Decide whether planned vertical implementation work should ship as independent pull requests or as a stack of small ordered pull requests, then plan, build, review, update, and merge the stack safely.
When should I use Stack Pull Requests?
Stack Pull Requests fits situations like: one slice is too large for effective review; later slices should proceed on the same evolving baseline before earlier pull requests merge; AI-generated code volume needs deliberate review boundaries; A plan already defines dependent pull request boundaries.
How do I install Stack Pull Requests in Claude Code?
Run `npx skills add citypaul/.dotfiles --skill stack-pull-requests -a claude-code`. Or copy the skill folder (claude/.claude/skills/stack-pull-requests in citypaul/.dotfiles) into .claude/skills/stack-pull-requests in your project. Claude Code loads it when a task matches its description.
How do I install Stack Pull Requests in Codex?
Run `npx skills add citypaul/.dotfiles --skill stack-pull-requests -a codex`. Or copy the skill folder (claude/.claude/skills/stack-pull-requests in citypaul/.dotfiles) into .agents/skills/stack-pull-requests in your project. Codex loads it when a task matches its description.
Can I use Stack Pull Requests in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add citypaul/.dotfiles --skill stack-pull-requests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stack-pull-requests, .gemini/skills/stack-pull-requests, .github/skills/stack-pull-requests and .opencode/skills/stack-pull-requests in your project.
What does Stack Pull Requests need to run?
Going by SKILL.md and its folder, Stack Pull Requests needs the command-line tools its instructions call (gh).
Does Stack Pull Requests access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Stack Pull Requests safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Stack Pull Requests use?
Stack Pull Requests has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Stack Pull Requests use?
About 6.2k tokens (SKILL.md is roughly 25k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Stack Pull Requests?
Skills that share tags, products or a category with Stack Pull Requests: Aidd Review (paralleldrive/aidd, 384 stars), QA (wp-media/wp-rocket, 767 stars), Acceptance Criteria Check (shopsys/shopsys, 350 stars) and Finishing a Development Branch (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stack Pull Requests?
citypaul (a GitHub user) maintains it in citypaul/.dotfiles, which has 739 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 2, 2026.
Source: citypaul/.dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.