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.
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
MITAuto-check passed
Install GitHub PR Workflow
$ npx skills add paperclipai/paperclip --skill github-pr-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install paperclipai/paperclip github-pr-workflow --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/paperclipai/paperclip.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow .claude/skills/github-pr-workflow && 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 "github-pr-workflow" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow into .claude/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", 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/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflowType 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 paperclipai/paperclip --skill github-pr-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install paperclipai/paperclip github-pr-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow .agents/skills/github-pr-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-pr-workflow" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow into .agents/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", 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 paperclipai/paperclip --skill github-pr-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install paperclipai/paperclip github-pr-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow .cursor/skills/github-pr-workflow && 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 "github-pr-workflow" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow into .cursor/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", 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/paperclipai/paperclip.git --path packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow--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 paperclipai/paperclip --skill github-pr-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install paperclipai/paperclip github-pr-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow .gemini/skills/github-pr-workflow && 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 "github-pr-workflow" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow into .gemini/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", 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 paperclipai/paperclip github-pr-workflowInstalls 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 paperclipai/paperclip --skill github-pr-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow .github/skills/github-pr-workflow && 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 "github-pr-workflow" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow into .github/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", 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 paperclipai/paperclip --skill github-pr-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install paperclipai/paperclip github-pr-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow .opencode/skills/github-pr-workflow && 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 "github-pr-workflow" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow into .opencode/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", 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
github-pr-workflow- GitHub stars
- 98k
- Token cost
- ~991 tokens
- SKILL.md length
- 479 words
- Files
- 1
- Skills in repo
- 60
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
- SKILL.md covers When to use, When not to use, Branch hygiene before opening and PR title, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
GitHub PR Workflow is an agent skill from paperclipai/paperclip. Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with GitHub. The repository describes itself as: The open-source app everyone uses to manage agents at work. The licence is MIT.
Example prompts
- “/github-pr-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 03cf6a6. 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 (its code samples are markdown).
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
GitHub PR Workflow loads about 991 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 479 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 paperclipai/paperclip at commit 03cf6a6, republished under its MIT licence (© paperclipai). 479 words, ~991 tokens.
Download SKILL.mdSave it as
.claude/skills/github-pr-workflow/SKILL.md (or your agent's skills folder).- name
- github-pr-workflow
- description
- Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
- key
- paperclipai/bundled/software-development/github-pr-workflow
- recommendedForRoles
- engineer
- tags
- github, pull-requests, code-review, release
GitHub Pull Request Workflow
Ship a PR a reviewer can land without follow-up clarifying questions. The aim is high signal in the title and body, evidence the change works, and clean replies when feedback comes in.
When to use
- You are about to open a PR for a change that is functionally complete.
- A reviewer left comments and you need to respond and push fixes.
- A PR has been open more than a day and needs to be brought back into shape (stale conflicts, missing description, missing verification).
When not to use
- The change is not yet functionally complete. Finish the work first; draft PRs that bounce on review are noise.
- The repository uses a non-GitHub forge. Adjust to that forge's conventions; do not force GitHub-isms.
Branch hygiene before opening
- Rebase or merge from the target base so the diff is current.
- Squash WIP commits into reviewable units. Prefer one commit per logical change; do not force one-commit-per-PR if the work is genuinely multi-step.
- Confirm tests, typecheck, and lint pass locally. Note any deliberate skips in the PR body.
- Remove debug prints, commented-out code, and
TODOmarkers that are not tracked.
PR title
- Imperative mood, under 70 characters.
- Lead with the user-visible change, not the file touched.
Allow CSV export from reports tablebeatsUpdate reports.tsx. - If the repo uses an issue prefix convention (
PAP-1234:,[security]), follow it. - No trailing period.
PR body
Use this structure:
## Summary
- 1–3 bullets describing what changed and why.
## Implementation notes
- Anything non-obvious in the diff: trade-offs, dropped alternatives, gotchas.
- Migration or config implications.
## Verification
- The exact commands or steps you ran.
- Screenshots or short clips for UI changes (required if pixels moved).
- Edge cases you exercised by hand.
## Risk and rollback
- What breaks if this is reverted, and how to revert cleanly.Skip the Risk and rollback section only for clearly trivial PRs (typos, docs).
Verification evidence
- Tests passing in CI is necessary, not sufficient. Reviewers also need to know the change behaves correctly end to end.
- For UI work, include screenshots of the golden path and one edge case. Tag dark and light mode if the project supports both.
- For migrations, include a dry-run plan and reversal steps.
- For performance changes, include a before/after measurement, not adjectives.
Show full SKILL.md (167 more words)Show less
Replying to review comments
- Reply on every comment, even with just "fixed in
<commit-sha>" — silent fixes leave the reviewer guessing. - Push fixes as new commits while review is active; do not amend during review unless the reviewer agrees.
- If you disagree with feedback, say so with one sentence of rationale and let the reviewer decide. Don't escalate over comments.
- Re-request review explicitly after pushing changes.
Merge checklist
- All required checks green.
- All review comments resolved.
- PR title/body still accurate (update if scope changed mid-review).
- Linked issue moves to
in_reviewordoneper project convention. - Delete the branch after merge unless it is a long-lived integration branch.
Anti-patterns
- PR description that says "see commits". Reviewers should not need to read the log.
- Mixing refactor and behavior change in the same PR with no separation in the body.
- "Address feedback" commits that bundle unrelated edits. One commit per round of feedback is fine; one commit for everything in flight is not.
- Force-pushing during active review without telling the reviewer.
© paperclipai, 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 packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow of paperclipai/paperclip.
Open the folder on GitHubat commit 03cf6a6
Compare with similar skills
GitHub PR Workflow 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 |
|---|---|---|---|---|---|---|
| GitHub PR Workflow this skillpaperclipai/paperclip | 98k | — | ~991 | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
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 paperclipai/paperclip
All 60 skills in this repoGarden Inbox
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
Paperclip
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
Paperclip
paperclipai/paperclip
A skill your agent uses for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and…
Design Guide
paperclipai/paperclip
Paperclip UI design system guide for building consistent, reusable frontend components.
Paperclip Page
paperclipai/paperclip
Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.
Paperclip Create Agent
paperclipai/paperclip
Create new agents in Paperclip with governance-aware hiring.
Related
Works with
Questions about GitHub PR Workflow
What does GitHub PR Workflow do?
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments. GitHub PR Workflow is an agent skill from paperclipai/paperclip. Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
How do I install GitHub PR Workflow in Claude Code?
Run `npx skills add paperclipai/paperclip --skill github-pr-workflow -a claude-code`. Or copy the skill folder (packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow in paperclipai/paperclip) into .claude/skills/github-pr-workflow in your project. Claude Code loads it when a task matches its description.
How do I install GitHub PR Workflow in Codex?
Run `npx skills add paperclipai/paperclip --skill github-pr-workflow -a codex`. Or copy the skill folder (packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow in paperclipai/paperclip) into .agents/skills/github-pr-workflow in your project. Codex loads it when a task matches its description.
Can I use GitHub PR Workflow 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 paperclipai/paperclip --skill github-pr-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-pr-workflow, .gemini/skills/github-pr-workflow, .github/skills/github-pr-workflow and .opencode/skills/github-pr-workflow in your project.
What does GitHub PR Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: GitHub PR Workflow is instructions for the agent only.
Does GitHub PR Workflow 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 GitHub PR Workflow 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 GitHub PR Workflow use?
GitHub PR Workflow 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 GitHub PR Workflow use?
About 991 tokens (SKILL.md is roughly 4k 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 GitHub PR Workflow?
Skills that share tags, products or a category with GitHub PR Workflow: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub PR Workflow?
paperclipai (a GitHub organization) maintains it in paperclipai/paperclip, which has 98,187 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 7, 2026.
Source: paperclipai/paperclip on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.