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.
Defines nestia branch, commit, pull-request, check, and merge workflows.
Install Pull Request
$ npx skills add samchon/nestia --skill pull-request -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install samchon/nestia pull-request --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/samchon/nestia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pull-request .claude/skills/pull-request && 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 "pull-request" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/pull-request into .claude/skills/pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request", 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/samchon/nestia/tree/master/.agents/skills/pull-requestType 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 samchon/nestia --skill pull-request -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install samchon/nestia pull-request --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pull-request .agents/skills/pull-request && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pull-request" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/pull-request into .agents/skills/pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request", 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 samchon/nestia --skill pull-request -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install samchon/nestia pull-request --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pull-request .cursor/skills/pull-request && 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 "pull-request" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/pull-request into .cursor/skills/pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request", 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/samchon/nestia.git --path .agents/skills/pull-request--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 samchon/nestia --skill pull-request -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install samchon/nestia pull-request --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pull-request .gemini/skills/pull-request && 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 "pull-request" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/pull-request into .gemini/skills/pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request", 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 samchon/nestia pull-requestInstalls 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 samchon/nestia --skill pull-request -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pull-request .github/skills/pull-request && 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 "pull-request" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/pull-request into .github/skills/pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request", 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 samchon/nestia --skill pull-request -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install samchon/nestia pull-request --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pull-request .opencode/skills/pull-request && 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 "pull-request" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/pull-request into .opencode/skills/pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request", 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
pull-request- GitHub stars
- 2.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 845 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Defines nestia branch, commit, pull-request, check, and merge workflows.
- The user explicitly asks to open
- SKILL.md covers Branch From The Target, Commit Logical Units, Write The Pull Request and Version Bumps Are Release…, plus 3 more sections
- Calls pnpm
- Merge a pull request
What it does
Pull Request is an agent skill from samchon/nestia. Defines nestia branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push, update, or merge one on unprompted initiative.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: NestJS Helper + AI Chatbot Development. The licence is MIT.
When your agent uses it
- The user explicitly asks to open
- Merge a pull request
- A standing autonomous mandate authorizes end-to-end delivery
- Merge one on unprompted initiative
Example prompts
- “Use the pull-request skill to define nestia branch, commit, pull-request, check, and merge workflows”
- “/pull-request”
What it can do on your machine
Read from SKILL.md and the folder at commit d3627e8. 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:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, 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
Pull Request loads about 1.6k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 845 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 samchon/nestia at commit d3627e8, republished under its MIT licence (© samchon). 845 words, ~1,577 tokens.
Download SKILL.mdSave it as
.claude/skills/pull-request/SKILL.md (or your agent's skills folder).- name
- pull-request
- description
- Defines nestia branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push, update, or merge one on unprompted initiative.
Pull Request Submission
Act on this skill only when the user explicitly requests the corresponding remote action, or when a standing autonomous mandate authorizes it. Permission to edit locally is not permission to push or open a pull request, and permission to open or update is not permission to merge. The one exception is a standing autonomous mandate — an autonomous or remote-control campaign, or an explicit instruction to carry the work through merge: it is the request for every step it names, including push and merge, and the skill's check, verification, and self-review gates still apply to each step.
For an explicit continuation under issue #1775, follow its campaign procedure: keep the existing branch, pull request and checkout, with ordinary CI. Generic new-branch, worktree and CI-cancellation instructions do not apply to that campaign.
Branch From The Target
Branch from the pull-request target (master unless stated otherwise); never commit or push directly to the target. Name the branch for the merged outcome with the repository's established type and scope, such as feat/<scope>, fix/<scope>, docs/<scope>, or ci/<scope>.
Solo work never creates a clone or worktree; only an explicit multi-agent campaign batch owns one. If the current checkout contains unrelated or protected work, stage only the authorized paths; if that cannot keep the pull request isolated, report the conflict rather than stashing, reverting, mixing, or relocating the work.
Commit Logical Units
Use one commit per coherent unit when the diff is large. Follow the repository's <type>(<scope>): <subject> history with an imperative lowercase subject and no trailing period.
Run the validation the development skill requires. Formatting belongs to the final changes before merge, not to each commit or push.
Stage explicit paths when the worktree is mixed. Never include unrelated user changes silently.
Write The Pull Request
Write the body at open as the historical intent statement. Include the intent, scope, deferred items, and exact local verification. State skipped checks and disabled campaign CI honestly.
Do not rewrite the body after every follow-up push. Record later CI fixes, newly discovered design issues, promoted deferred work, and Self-Review results as formal GitHub pull-request reviews with the COMMENT event so the thread preserves chronology. Use inline review comments when an observation belongs to a changed line and the review body for commit-wide or round-wide results. Do not use ordinary issue-style pull-request comments for this ledger, and never APPROVE or REQUEST_CHANGES on your own pull request. The title describes the merged outcome in Conventional Commits style, not the work process.
Push only the topic branch with upstream tracking. Use a file-backed body for multiline Markdown when opening through gh.
An ordinary pull request carries one GitHub issue unless two issues are genuinely the same defect. Issue campaigns override that boundary: a solo cycle pull request owns every implementation-ready issue in the cycle, and a multi-agent batch owns its admitted set. Record verification and any known gap in the body.
Version Bumps Are Release Commits
bumpp -r through pnpm release owns version numbers across the workspace, so do not hand-edit a version field in an ordinary pull request. The development skill's Change Integrity rules state when a native change earns a new version and who assigns it.
Show full SKILL.md (316 more words)Show less
Issue Campaign Override
Before any issue-campaign push or pull request, complete the applicable steps of .agents/skills/issue-campaign/development.md; its final formatting step remains a merge gate. A solo campaign uses one cycle pull request and the ordinary check loop, plus its integration-sensitive gate. Only .agents/skills/multi-agent/issue-campaign.md overrides that flow with worktree batches, exact-SHA campaign-run cancellation, local implementation gates, and Post-Campaign Cleanup.
Watch Checks After Every Ordinary Push
After each ordinary push, including every Post-Campaign Cleanup push, monitor the pull-request checks until every check settles. Only CI-suspended campaign implementation waves skip this loop. On failure, fetch the relevant job log, diagnose the real cause, fix it in place, push a new commit, and resume monitoring. Do not treat a green unrelated job as acceptance for a failed required surface.
The single test.yml job checks Evidence, Go, unit and E2E populations after shared preparation. Check every test step; a successful unit step does not establish SDK generation, installed-consumer behavior or declaration acknowledgments. Do not split tests into a workflow matrix or separate test workflows. Record the actual job duration against the eight-minute target.
Merge On Explicit Request Or Standing Autonomous Mandate
Do not merge, squash-merge, rebase, or update the target branch on unprompted initiative. Merge when the user explicitly asks, or when a standing autonomous mandate authorizes end-to-end delivery; use the repository's established merge method unless another is specified. Under an autonomous mandate the author that owns the pull request merges it themselves once the merge gate below passes, without separate approval.
Before merging, apply the development skill's final formatting rule and include any resulting changes in the pull-request head. Confirm required checks pass on that final head for an ordinary or Post-Campaign Cleanup pull request. For a multi-agent campaign implementation pull request whose automatic CI is deliberately suspended, confirm its local-verification, independent-verification, and integration gates instead. If branch protection blocks the requested merge, report the blocker rather than bypassing it.
© samchon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/pull-request of samchon/nestia.
Open the folder on GitHubat commit d3627e8
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in samchon/nestia, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Pull Request 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 |
|---|---|---|---|---|---|---|
| Pull Request this skillsamchon/nestia | 2.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| 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 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
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.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
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.
More from samchon/nestia
All 10 skills in this repoProject
samchon/nestia
Defines the nestia product contract, workspace layout, package boundaries, the Go plugin composition model, and canonical commands.
Contracts
samchon/nestia
Defines self-acknowledgments for production declarations and tests.
Issue Campaign
samchon/nestia
Defines the default solo repository-wide issue campaign for nestia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo…
Review
samchon/nestia
Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia.
Development
samchon/nestia
Defines nestia implementation rules, testing standards, validation, consequence analysis, and change integrity.
Discussion
samchon/nestia
Runs structured multi-agent discussions for open-ended nestia topics.
Related
Categories
Questions about Pull Request
What does Pull Request do?
Defines nestia branch, commit, pull-request, check, and merge workflows. Pull Request is an agent skill from samchon/nestia. Defines nestia branch, commit, pull-request, check, and merge workflows.
When should I use Pull Request?
Pull Request fits situations like: the user explicitly asks to open; merge a pull request; A standing autonomous mandate authorizes end-to-end delivery; merge one on unprompted initiative.
How do I install Pull Request in Claude Code?
Run `npx skills add samchon/nestia --skill pull-request -a claude-code`. Or copy the skill folder (.agents/skills/pull-request in samchon/nestia) into .claude/skills/pull-request in your project. Claude Code loads it when a task matches its description.
How do I install Pull Request in Codex?
Run `npx skills add samchon/nestia --skill pull-request -a codex`. Or copy the skill folder (.agents/skills/pull-request in samchon/nestia) into .agents/skills/pull-request in your project. Codex loads it when a task matches its description.
Can I use Pull Request 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 samchon/nestia --skill pull-request -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pull-request, .gemini/skills/pull-request, .github/skills/pull-request and .opencode/skills/pull-request in your project.
What does Pull Request need to run?
Going by SKILL.md and its folder, Pull Request needs the command-line tools its instructions call (pnpm).
Does Pull Request 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 Pull Request 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 Pull Request use?
Pull Request is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pull Request use?
About 1.6k tokens (SKILL.md is roughly 6.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 Pull Request?
Skills that share tags, products or a category with Pull Request: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pull Request?
samchon (a GitHub user) maintains it in samchon/nestia, which has 2,179 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: samchon/nestia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.