Full PR Lifecycle (work-with-pr)
Splits a task into the smallest mergeable PRs, builds each in its own git worktree with evidence-backed manual QA, then loops on CI and review-bot gates until merged and cleaned up.
Dev & CodingAdvanced★ 67,531⑂ 5,507AI score 8/10Last updated: Aug 9, 2026
What it does
- Atomic PR splitting: decomposes one task into the smallest PRs that each compile, pass, and stand alone; independent slices run in parallel via subagents or a team.
- Isolated worktrees: one branch + git worktree per PR, created as a sibling of the repo so your main working directory (and any uncommitted work) stays untouched.
- Evidence-bound QA: a green test suite is explicitly not enough — you must drive the real surface (tmux / HTTP / browser / GUI) and write the evidence file to disk before committing or pushing.
- Reviewer-ready PR body: an English template with Summary / Changes / QA & Evidence / Risks & Residuals / Related Issues, plus rules against pasting secret-bearing logs.
- Unbounded verification loop: Gate A (CI via
gh pr checks) and Gate B (the Cubic review bot), where a failure routes you back to fix-and-re-QA and Cubic is skipped only when its quota is exhausted. - Merge & cleanup: arms auto-merge by default, blocks until the PR is actually MERGED, syncs state back, then removes and prunes the worktree.
Who it's for
- Teams with a strict PR review culture who want consistent, auditable PRs
- Developers tired of 2000-line PRs that get rubber-stamped
- Anyone already using GitHub CLI, CI checks and an automated review bot
- Engineers running several PRs in parallel during a large refactor
Examples
- "Implement this issue and open a PR" → split into three atomic PRs, one worktree each, build the independent ones concurrently, merge in dependency order.
- "CI is red, fix it" → pull failed job logs with
gh run view --log-failed, fix only the identified issue, commit atomically, push, re-verify from Gate A. - "Address the review bot comments" → parse the Cubic review, separate false positives from real issues, fix, capture fresh QA evidence if behavior changed, re-enter the loop.
Note: it assumes a specific setup (
bun,ghCLI, adevbase branch, the Cubic bot, theulw-loopskill), so adapt those parts to your repository.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/HEAD/.opencode/skills/work-with-pr/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the .opencode/skills/work-with-pr folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/code-yeongyu-work-with-pr/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/code-yeongyu/oh-my-openagent /tmp/oh-my-openagent && mkdir -p ~/.claude/skills/work-with-pr && cp -r /tmp/oh-my-openagent/.opencode/skills/work-with-pr/* ~/.claude/skills/work-with-pr/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal and clone the repository into a temp folder:
git clone https://github.com/code-yeongyu/oh-my-openagent /tmp/oh-my-openagent - Create the Claude Code skill directory:
mkdir -p ~/.claude/skills/work-with-pr - Copy the skill files over:
cp -r /tmp/oh-my-openagent/.opencode/skills/work-with-pr/* ~/.claude/skills/work-with-pr/ - Check prerequisites: GitHub CLI authenticated (
gh auth login), push access to the repo, and your project's package manager (e.g.bun) installed. - Open
~/.claude/skills/work-with-pr/SKILL.mdand adjustBASE_BRANCH="dev", thebuncommands, and the Cubic-bot section to match your repository's conventions. - Restart Claude Code, then ask something like "implement this and open a PR" to trigger the skill.
View source on GitHub ↗License: NOASSERTION