Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Process PR based on code review - if approved, create follow-up issues, merge, close; if changes requested, re-run implement-issue
$ npx skills add aaddrick/claude-pipeline --skill process-pr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aaddrick/claude-pipeline process-pr --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/aaddrick/claude-pipeline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/process-pr .claude/skills/process-pr && 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 "process-pr" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/process-pr into .claude/skills/process-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-pr", 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/aaddrick/claude-pipeline/tree/main/.claude/skills/process-prType 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 aaddrick/claude-pipeline --skill process-pr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aaddrick/claude-pipeline process-pr --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/process-pr .agents/skills/process-pr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "process-pr" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/process-pr into .agents/skills/process-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-pr", 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 aaddrick/claude-pipeline --skill process-pr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aaddrick/claude-pipeline process-pr --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/process-pr .cursor/skills/process-pr && 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 "process-pr" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/process-pr into .cursor/skills/process-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-pr", 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/aaddrick/claude-pipeline.git --path .claude/skills/process-pr--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 aaddrick/claude-pipeline --skill process-pr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aaddrick/claude-pipeline process-pr --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/process-pr .gemini/skills/process-pr && 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 "process-pr" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/process-pr into .gemini/skills/process-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-pr", 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 aaddrick/claude-pipeline process-prInstalls 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 aaddrick/claude-pipeline --skill process-pr -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/process-pr .github/skills/process-pr && 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 "process-pr" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/process-pr into .github/skills/process-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-pr", 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 aaddrick/claude-pipeline --skill process-pr -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aaddrick/claude-pipeline process-pr --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/process-pr .opencode/skills/process-pr && 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 "process-pr" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/process-pr into .opencode/skills/process-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-pr", 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.
process-prProcess PR based on code review - if approved, create follow-up issues, merge, close; if changes requested, re-run implement-issue
Process PR is an agent skill from aaddrick/claude-pipeline. Process PR based on code review - if approved, create follow-up issues, merge, close; if changes requested, re-run implement-issue
Its SKILL.md is about 2.7k 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. The repository describes itself as: Portable Claude Code multi-agent pipeline - skills, agents, hooks, orchestration scripts, and quality gates. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 402eac7. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghgitclaudeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Process PR loads about 2.7k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 639 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.
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.
The full file from aaddrick/claude-pipeline at commit 402eac7, republished under its MIT licence (© aaddrick). 639 words, ~2,739 tokens.
.claude/skills/process-pr/SKILL.md (or your agent's skills folder).Read PR review comments and act accordingly: if approved, create follow-up issues and merge; if changes requested, re-run implementation.
Announce at start: "Using process-pr to process PR #$1 for issue #$2"
Arguments:
$1 — PR number (required)$2 — Issue number that the PR addresses (required)$3 — Base branch for re-implementation if needed (required)Examples:
/process-pr 142 130 aw-next/process-pr 456 123 maindigraph process_pr {
rankdir=TB;
node [shape=box];
validate [label="1. Validate inputs"];
fetch [label="2. Fetch PR & review comments"];
check [label="3. Check review status"];
approved [label="Approved path"];
changes [label="Changes requested path"];
merge [label="4a. Squash merge PR"];
comment [label="4b. Comment on issue"];
close [label="4c. Close issue"];
delete [label="4d. Delete branch"];
parse [label="4e. Parse comments for follow-ups"];
create_issues [label="4f. Create follow-up issues"];
rerun [label="5. Re-run /implement-issue"];
output_success [label="Output: Success summary"];
output_rerun [label="Output: Re-implementation started"];
validate -> fetch -> check;
check -> approved [label="approved"];
check -> changes [label="changes requested"];
approved -> merge -> comment -> close -> delete -> parse -> create_issues -> output_success;
changes -> rerun -> output_rerun;
}Why merge first: Follow-up issues should only be created if the merge succeeds. Creating issues before merge can leave orphaned issues if merge fails (conflict, permissions, etc.). Merging first ensures we only create follow-ups for work that actually landed.
# Verify PR exists and is open
gh pr view $PR_NUMBER --json state,number,title,headRefName,reviews
# Verify issue exists and is open
gh issue view $ISSUE_NUMBER --json state,number,titleIf validation fails: Stop and report error.
# Get PR with comments
gh pr view $PR_NUMBER --json number,title,state,headRefName,comments
# Also get the full PR view with comments for parsing
gh pr view $PR_NUMBER --repo OWNER/REPO --commentsExtract:
IMPORTANT: Review status is embedded in PR comments by the implement-issue skill. Use this explicit algorithm:
Step 3a: Fetch all PR comments
# Get comments as JSON array
COMMENTS=$(gh pr view $PR_NUMBER --json comments --jq '.comments[].body')Step 3b: Extract status from comments (most recent wins)
# Parse status using explicit algorithm
parse_review_status() {
local comments="$1"
local status=""
# Process comments in order (last one wins)
while IFS= read -r comment; do
# Check for markdown bold format first (preferred)
if echo "$comment" | grep -q '\*\*Status: APPROVED\*\*'; then
status="APPROVED"
elif echo "$comment" | grep -q '\*\*Status: CHANGES_REQUESTED\*\*'; then
status="CHANGES_REQUESTED"
# Fallback to plain text format
elif echo "$comment" | grep -q 'Status: APPROVED'; then
status="APPROVED"
elif echo "$comment" | grep -q 'Status: CHANGES_REQUESTED'; then
status="CHANGES_REQUESTED"
fi
done <<< "$comments"
echo "$status"
}
REVIEW_STATUS=$(parse_review_status "$COMMENTS")Step 3c: Validate status
if [ -z "$REVIEW_STATUS" ]; then
echo "ERROR: No review status found in PR #$PR_NUMBER comments"
echo "Expected: Comment containing '**Status: APPROVED**' or '**Status: CHANGES_REQUESTED**'"
exit 1
fi
echo "Review status: $REVIEW_STATUS"Status priority:
**Status: APPROVED** (markdown bold - preferred)**Status: CHANGES_REQUESTED** (markdown bold - preferred)Status: APPROVED (plain text - fallback)Status: CHANGES_REQUESTED (plain text - fallback)Multiple reviews: The algorithm processes comments in chronological order. The LAST status found wins, representing the most recent review.
gh pr merge $PR_NUMBER \
--squash \
--delete-branchIf merge fails:
gh issue comment $ISSUE_NUMBER --body "$(cat <<'EOF'
## Completed
Resolved via PR #$PR_NUMBER (squash merged).
### Follow-up issues created:
- #XXX - Description
- #YYY - Description
(Or "No follow-up issues needed.")
EOF
)"gh issue close $ISSUE_NUMBERVerify closure:
gh issue view $ISSUE_NUMBER --json stateThe --delete-branch flag handles this. Verify:
git ls-remote --heads origin $BRANCH_NAMEIf still exists:
git push origin --delete $BRANCH_NAMEScan all review comments for indicators of follow-up work:
Trigger phrases:
Extract for each:
For each extracted issue:
gh issue create \
--repo OWNER/REPO \
--title "$ISSUE_TITLE" \
--body "$(cat <<'EOF'
## Context
Created from code review of PR #$PR_NUMBER (Issue #$ISSUE_NUMBER)
## Description
$EXTRACTED_DESCRIPTION
## References
- Parent Issue: #$ISSUE_NUMBER
- PR: #$PR_NUMBER
- Reviewer: @$REVIEWER
EOF
)" \
--label "$LABELS"Log each: Created follow-up issue #XXX: "$TITLE"
When the code reviewer requests changes, spawn a new implementation session:
claude --dangerously-skip-permissions \
--print \
"/implement-issue $ISSUE_NUMBER $BASE_BRANCH" \
2>&1 | tee -a logs/process-pr-rerun-$(date +%Y%m%d-%H%M%S).logNotes:
/process-pr again to check the new reviewLog:
Changes requested on PR #$PR_NUMBER. Re-running implementation for issue #$ISSUE_NUMBER...## Process PR Complete
**PR:** #$PR_NUMBER
**Issue:** #$ISSUE_NUMBER
**Status:** ✅ Merged
### Actions Taken
- [x] Review status: APPROVED
- [x] Created N follow-up issues
- [x] PR squash merged
- [x] Issue #$ISSUE_NUMBER closed
- [x] Branch deleted
### Follow-up Issues Created
| Issue | Title | Labels |
|-------|-------|--------|
| #XXX | Description | enhancement |## Process PR: Changes Requested
**PR:** #$PR_NUMBER
**Issue:** #$ISSUE_NUMBER
**Status:** 🔄 Re-implementing
### Review Feedback
$REVIEW_COMMENTS_SUMMARY
### Action
Re-running /implement-issue $ISSUE_NUMBER $BASE_BRANCH to address requested changes.| Failure Point | Action |
|---|---|
| Validation fails | Stop, report error |
| No review status in comments | Stop, report - need code review comment with Status line first |
| Issue creation fails | Log warning, continue |
| Merge fails | Stop, return failure, do NOT close issue |
| Issue close fails | Log warning (merge succeeded) |
| Branch delete fails | Log warning (best-effort) |
| Re-implementation fails | Log error, include in output |
Called by:
handle-issues skill (after implement-issue creates PR)/process-pr <pr> <issue> <branch>Calls:
/implement-issue (when changes requested)Requires:
gh CLI authenticated**Status: APPROVED** or **Status: CHANGES_REQUESTED**User: /process-pr 142 130 aw-next
Claude: Using process-pr to process PR #142 for issue #130
Validating... PR #142 open, Issue #130 open
Parsing comments... Status: APPROVED, 1 follow-up found
Creating issue #145: "Add rate limiting to auth endpoint"
Merging PR #142... Squash merge successful
Closing issue #130... done
Deleting branch issue-130-auth-redirect... done
## Process PR Complete
PR: #142 | Issue: #130 | Status: Merged
Follow-up: #145 - Add rate limiting to auth endpointUser: /process-pr 142 130 aw-next
Claude: Using process-pr to process PR #142 for issue #130
Validating... PR #142 open, Issue #130 open
Parsing comments... Status: CHANGES_REQUESTED
Feedback: "Need to handle edge case when session expires"
Re-running /implement-issue 130 aw-next...
[spawns headless session]When invoked via batch-orchestrator.sh with --json-schema, this skill's output is parsed for structured data. To ensure reliable extraction, always end your execution with a clear result statement.
At the very end of execution, output a clear status summary. This helps --json-schema reliably extract the structured output.
On successful merge:
## Result
Status: merged
Follow-up issues: #145, #146On merge with no follow-ups:
## Result
Status: merged
Follow-up issues: noneOn changes requested:
## Result
Status: changes_requestedOn error:
## Result
Status: error
Error: Merge failed - conflict with base branchOn rate limit:
## Result
Status: rate_limit
Error: GitHub API rate limit exceededThe batch-orchestrator.sh uses this JSON schema to extract results:
{
"type": "object",
"properties": {
"status": {"enum": ["merged", "changes_requested", "error", "rate_limit"]},
"follow_up_issues": {"type": "array", "items": {"type": "integer"}},
"error": {"type": "string"}
},
"required": ["status"]
}Important: The final result section must be the last significant output. The --json-schema flag asks Claude to summarize the execution according to this schema, so ending with a clear status makes extraction reliable.
© aaddrick, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/process-pr of aaddrick/claude-pipeline.
Open the folder on GitHubat commit 402eac7
Process PR 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 |
|---|---|---|---|---|---|---|
| Process PR this skillaaddrick/claude-pipeline | 130 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
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.
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
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.
aaddrick/claude-pipeline
A skill your agent uses when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool
aaddrick/claude-pipeline
A skill your agent uses when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack…
aaddrick/claude-pipeline
A skill your agent uses when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code
aaddrick/claude-pipeline
Comprehensive UI/CSS review using parallel agents. An agent skill from aaddrick/claude-pipeline.
aaddrick/claude-pipeline
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in .worktrees/
aaddrick/claude-pipeline
A skill your agent uses when given a GitHub issue number and base branch to implement end-to-end
Categories
Process PR based on code review - if approved, create follow-up issues, merge, close; if changes requested, re-run implement-issue. Process PR is an agent skill from aaddrick/claude-pipeline.
Process PR fits situations like: development work in your project.
Run `npx skills add aaddrick/claude-pipeline --skill process-pr -a claude-code`. Or copy the skill folder (.claude/skills/process-pr in aaddrick/claude-pipeline) into .claude/skills/process-pr in your project. Claude Code loads it when a task matches its description.
Run `npx skills add aaddrick/claude-pipeline --skill process-pr -a codex`. Or copy the skill folder (.claude/skills/process-pr in aaddrick/claude-pipeline) into .agents/skills/process-pr in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aaddrick/claude-pipeline --skill process-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/process-pr, .gemini/skills/process-pr, .github/skills/process-pr and .opencode/skills/process-pr in your project.
Going by SKILL.md and its folder, Process PR needs the command-line tools its instructions call (gh, git and claude).
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Process PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Process PR: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
aaddrick (a GitHub user) maintains it in aaddrick/claude-pipeline, which has 130 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on February 25, 2026.
Source: aaddrick/claude-pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.