work-with-pr

Solid

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 to land as a PR. Triggers: 'create a PR', 'implement and PR', 'work on this and make a PR', 'implement issue', 'land this as a PR', 'split into atomic PRs', 'parallel PRs', 'work-with-pr', 'PR workflow', 'implement end to end', even when user just says 'implement X' if the context implies PR delivery.

AI & Automation 68,941 stars 5670 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 83/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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: Cubic → cubic-dev-ai[bot] "No issues found" (SKIPPED, not failed, when Cubic's quota is exhausted) Phase 4: Merge → Auto-merge by default; wait until actually merged, then worktree cleanup ``` </architect...

Details

Author
code-yeongyu
Repository
code-yeongyu/oh-my-openagent
Created
9 months ago
Last Updated
today
Language
TypeScript
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

work-with-pr

Full PR lifecycle for oh-my-matrix in a task-owned git worktree — implement with evidence-bound QA, open a reviewer-readable PR against `master`, then run an unbounded verify loop over three gates (CI / review-work / docs-build) until all pass, then merge by default and clean up the worktree. Decomposes work into the smallest atomic, independently-mergeable PRs and builds the independent ones concurrently. Use whenever implementation work needs to land as a PR. Triggers: 'create a PR', 'implement and PR', 'land this', 'work-with-pr', 'implement issue', 'split into atomic PRs', 'parallel PRs', even 'implement X' when the context implies PR delivery.

3 Updated yesterday
TeFuirnever
AI & Automation Listed

pr-workflow

Use when creating PRs, finishing features, or preparing code for merge. Use after local work is complete and ready for review/deployment. Not a Workflow wrapper; this is a session-long process skill.

0 Updated today
schmug
Code & Development Listed

issue-to-pr

Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline (design hardening, tests green, code-review clean), scaling the machinery to the task's tier and asking at most one batched question. Auto-links the issue to close on merge, advances the board card, then merges and cleans up once you approve the PR in-session. Triggers: "take task N", "work on issue #N", "do the next task", "build/fix X" when no issue exists yet, and — for the merge gate later — "merge it", "approve the PR", "ship it", "lgtm merge".

7 Updated 2 days ago
DmitriyYukhanov