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.
Review repository changes as they would be reviewed in a pull request.
Install Stacks PR Review
$ npx skills add stacks-network/stacks-core --skill stacks-pr-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stacks-network/stacks-core stacks-pr-review --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/stacks-network/stacks-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/stacks-pr-review .claude/skills/stacks-pr-review && 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 "stacks-pr-review" agent skill from https://github.com/stacks-network/stacks-core/tree/main/.agents/skills/stacks-pr-review into .claude/skills/stacks-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-pr-review", 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/stacks-network/stacks-core/tree/main/.agents/skills/stacks-pr-reviewType 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 stacks-network/stacks-core --skill stacks-pr-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stacks-network/stacks-core stacks-pr-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacks-network/stacks-core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/stacks-pr-review .agents/skills/stacks-pr-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stacks-pr-review" agent skill from https://github.com/stacks-network/stacks-core/tree/main/.agents/skills/stacks-pr-review into .agents/skills/stacks-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-pr-review", 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 stacks-network/stacks-core --skill stacks-pr-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stacks-network/stacks-core stacks-pr-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacks-network/stacks-core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/stacks-pr-review .cursor/skills/stacks-pr-review && 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 "stacks-pr-review" agent skill from https://github.com/stacks-network/stacks-core/tree/main/.agents/skills/stacks-pr-review into .cursor/skills/stacks-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-pr-review", 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/stacks-network/stacks-core.git --path .agents/skills/stacks-pr-review--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 stacks-network/stacks-core --skill stacks-pr-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stacks-network/stacks-core stacks-pr-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacks-network/stacks-core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/stacks-pr-review .gemini/skills/stacks-pr-review && 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 "stacks-pr-review" agent skill from https://github.com/stacks-network/stacks-core/tree/main/.agents/skills/stacks-pr-review into .gemini/skills/stacks-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-pr-review", 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 stacks-network/stacks-core stacks-pr-reviewInstalls 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 stacks-network/stacks-core --skill stacks-pr-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stacks-network/stacks-core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/stacks-pr-review .github/skills/stacks-pr-review && 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 "stacks-pr-review" agent skill from https://github.com/stacks-network/stacks-core/tree/main/.agents/skills/stacks-pr-review into .github/skills/stacks-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-pr-review", 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 stacks-network/stacks-core --skill stacks-pr-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stacks-network/stacks-core stacks-pr-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacks-network/stacks-core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/stacks-pr-review .opencode/skills/stacks-pr-review && 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 "stacks-pr-review" agent skill from https://github.com/stacks-network/stacks-core/tree/main/.agents/skills/stacks-pr-review into .opencode/skills/stacks-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stacks-pr-review", 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
stacks-pr-review- GitHub stars
- 3.1k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 557 words
- Files
- 2
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Review repository changes as they would be reviewed in a pull request.
- Works in 5 steps: Determine the repository root and… → Determine the pull request's base branch… → Include committed changes from the merge… → …
- Asked to review my changes
- SKILL.md covers Establish the review scope, Load the authoritative review…, Review the changes and Report findings
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Stacks PR Review is an agent skill from stacks-network/stacks-core. Review repository changes as they would be reviewed in a pull request. Use when asked to review my changes, review code changes, pre-review a branch, review the current branch or a diff, review an open pull request, simulate PR feedback locally, or check committed, staged, unstaged, or untracked changes before a PR. Resolve and apply the repository's authoritative GitHub Copilot PR-review instructions without treating them as code-generation requirements.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Pull requests. It works with Bitcoin. The repository describes itself as: The Stacks blockchain implementation. The licence is GPL-3.0.
When your agent uses it
- Asked to review my changes
- Review code changes
- Pre-review a branch
- Review the current branch
Example prompts
- “/stacks-pr-review”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Determine the repository root and inspect the current branch and working-tree status.
- Determine the pull request's base branch from available PR metadata or branch configuration. If it cannot be determined reliably, infer…
- Include committed changes from the merge base with the base branch through HEAD in the review scope.
- For local reviews, also include staged and unstaged changes and relevant untracked files. Distinguish findings that apply only to…
- Build the complete changed-file list before selecting review instructions.
What it can do on your machine
Read from SKILL.md and the folder at commit 7e9da22. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Stacks PR Review loads about 1.1k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 557 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
The full file from stacks-network/stacks-core at commit 7e9da22, republished under its GPL-3.0 licence (© stacks-network). 557 words, ~1,086 tokens.
Download SKILL.mdSave it as
.claude/skills/stacks-pr-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- stacks-pr-review
- description
- Review repository changes as they would be reviewed in a pull request. Use when asked to review my changes, review code changes, pre-review a branch, review the current branch or a diff, review an open pull request, simulate PR feedback locally, or check committed, staged, unstaged, or untracked changes before a PR. Resolve and apply the repository's authoritative GitHub Copilot PR-review instructions without treating them as code-generation requirements.
Stacks PR review
Perform a read-only review of the requested changes and, for local reviews, relevant work not yet committed. Do not edit files unless the user separately asks for fixes.
Establish the review scope
- Determine the repository root and inspect the current branch and working-tree status.
- Determine the pull request's base branch from available PR metadata or branch configuration. If it cannot be determined reliably, infer the repository's default branch and state the assumption.
- Include committed changes from the merge base with the base branch through
HEADin the review scope. - For local reviews, also include staged and unstaged changes and relevant untracked files. Distinguish findings that apply only to uncommitted work when that distinction matters.
- Build the complete changed-file list before selecting review instructions.
If the user specifies a commit, range, branch, or subset of changed files, use that as the primary scope and say whether uncommitted changes were included. If the user names a pull request, use that pull request's diff against its base branch as the scope; include local uncommitted work only when explicitly requested, and distinguish it from the pull-request findings.
Treat IDE-provided selections and automatically attached editor context as focus context, not an implicit scope limit. Review the full requested change set and give that context particular attention; narrow the scope only when the user explicitly asks. If the request is solely to review existing selected code and identifies no change set, perform a normal code review rather than this diff-based workflow.
For local reviews without a PR description, use the user's request and commit messages as intent context alongside the changed code, tests, and documentation. State assumptions when the intended behavior remains unclear.
Load the authoritative review policy
- Read
.github/copilot-instructions.mdfor repository-wide review criteria. - Find every
*.instructions.mdfile under.github/instructions/. Read only each file's YAML frontmatter and match its comma-separatedapplyToglobs against the complete changed-file list. - Read and apply the full contents of every matching file. Apply all matches when scopes overlap; if none match, use only the repository-wide instructions. Do not read the bodies of unmatched files.
Treat the .github files as authoritative, and do not apply their review criteria as code-generation requirements.
Show full SKILL.md (187 more words)Show less
Review the changes
- Report only defects introduced or exposed by the selected diff; do not flag pre-existing issues the diff leaves unchanged.
- Inspect enough surrounding code, callers, tests, and documentation to validate each potential finding.
- Optionally run focused validation when it materially increases confidence and is safe in the current environment; use commands documented in
CONTRIBUTING.mdrather than generic tool defaults, and report what was and was not run.
Report findings
List actionable findings first, ordered by severity. For each finding:
- Give a concise title labelled critical (a merge-blocking risk of consensus failure, security compromise, irreversible data loss, or severe compatibility break), major (incorrect behavior with a realistic trigger and material user, protocol, data, security, or operational impact), or minor (a real defect with limited impact).
- Cite the changed file and the narrowest useful line location.
- Explain the triggering condition and concrete impact.
- Suggest a specific fix or validation when useful.
Avoid duplicate findings with the same root cause. After the findings, briefly state the reviewed scope, applicable instruction files, and validation performed. If there are no findings, say so explicitly and mention any material validation gaps.
© stacks-network, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/stacks-pr-review of stacks-network/stacks-core.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 7e9da22
Compare with similar skills
Stacks PR Review 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 |
|---|---|---|---|---|---|---|
| Stacks PR Review this skillstacks-network/stacks-core | 3.1k | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
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.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
Related
Works with
Categories
Questions about Stacks PR Review
What does Stacks PR Review do?
Review repository changes as they would be reviewed in a pull request. Stacks PR Review is an agent skill from stacks-network/stacks-core. Review repository changes as they would be reviewed in a pull request.
When should I use Stacks PR Review?
Stacks PR Review fits situations like: asked to review my changes; review code changes; pre-review a branch; review the current branch.
How do I install Stacks PR Review in Claude Code?
Run `npx skills add stacks-network/stacks-core --skill stacks-pr-review -a claude-code`. Or copy the skill folder (.agents/skills/stacks-pr-review in stacks-network/stacks-core) into .claude/skills/stacks-pr-review in your project. Claude Code loads it when a task matches its description.
How do I install Stacks PR Review in Codex?
Run `npx skills add stacks-network/stacks-core --skill stacks-pr-review -a codex`. Or copy the skill folder (.agents/skills/stacks-pr-review in stacks-network/stacks-core) into .agents/skills/stacks-pr-review in your project. Codex loads it when a task matches its description.
Can I use Stacks PR Review 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 stacks-network/stacks-core --skill stacks-pr-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stacks-pr-review, .gemini/skills/stacks-pr-review, .github/skills/stacks-pr-review and .opencode/skills/stacks-pr-review in your project.
What does Stacks PR Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Stacks PR Review is instructions for the agent only.
Does Stacks PR Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Stacks PR Review 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 Stacks PR Review use?
Stacks PR Review is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Stacks PR Review use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Stacks PR Review?
Skills that share tags, products or a category with Stacks PR Review: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stacks PR Review?
stacks-network (a GitHub organization) maintains it in stacks-network/stacks-core, which has 3,061 GitHub stars. The repository was last updated on October 8, 2026.
Source: stacks-network/stacks-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.