work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the smallest atomic, independently-mergeable PRs and builds the independent ones concurrently via one worktree per PR driven by parallel subagents or a team. Unbounded loop: any failing gate sends you back to fix-and-re-QA inside that PR's worktree. Use whenever implementation work needs
npx skills add code-yeongyu/oh-my-openagent --skill work-with-pr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Work With PR — Full PR Lifecycle You are executing a complete PR lifecycle: from fresh task-owned worktree setup, through `ulw-loop`-driven implementation with evidence-bound manual QA, PR creation, and an unbounded verification loop until the PR is merged. The loop has two gates — CI and Cubic — and a failing gate sends you back into that PR's worktree to fix and re-QA. You keep cycling until every active gate passes at once. **The unit of delivery is the smallest PR that compiles, passes, and stands on its own — not "one task, one PR."** A single task routinely splits into several atomic PRs; the lifecycle below describes ONE of them, so apply it to each, and build the independent ones concurrently (Phase 0). <architecture> ``` Phase 0: Setup → Split into atomic PRs, then branch + worktree per PR (parallel when independent) Phase 1: Implement → Drive the work through the ulw-loop skill: evidence-bound manual QA per success criterion, atomic commits Phase 2: PR Creation → Push, create a reviewer-readable English PR targeting dev Phase 3: Verify Loop → Unbounded iteration; a failing gate routes back to Phase 1: ├─ Gate A: CI → gh pr checks (bun test, typecheck, build) └─ Gate B:
- Phase 0: Setup
- 1. Decide the PR split
- 2. Resolve repository context
- 3. Create branch
- 4. Create worktree
- 5. Set working context
- Phase 1: Implement
- Scope discipline
- Commit strategy
- Pre-push local validation
- Phase 2: PR Creation
- Push and create PR
- Phase 3: Verification Loop
- Gate A: CI Checks
git fetch origin "$BASE_BRANCH" git branch "$BRANCH_NAME" "origin/$BASE_BRANCH" mkdir -p "$(dirname "$WORKTREE_PATH")" git worktree add "$WORKTREE_PATH" "$BRANCH_NAME" cd "$WORKTREE_PATH" If bun project: bun run typecheck bun test bun run build git push -u origin "$BRANCH_NAME"
What does the work-with-pr skill do?
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the smallest atomic, independently-mergeable PRs and builds the independent ones concurrently via one worktree per PR driven by parallel subagents or a team. Unbounded loop: any failing gate sends you back to fix-and-re-QA inside that PR's worktree. Use whenever implementation work needs
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill work-with-pr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.