work-with-pr
规范化提测与合并流程，适合团队协作场景
会创建分支、推送与合并，需仓库写权限且可能影响主分支
在独立 worktree 中执行完整 PR 的开发、验证、评审与合并生命周期
在独立的 git worktree 里完成一个完整 PR 的开发到合并流程：用 ulw-loop 实现代码、做手工 QA、产出面向 reviewer 的英文 PR 描述，跑 CI 和 Cubic 验证，验证不通过就回到同一 worktree 修复直到通过再合并并清理。适用于任何需要以 PR 形式落地的实现任务。它把大任务拆成最小可合并的 PR 并支持并行子代理或团队协作，确保可追溯和可反复验证。
▸ 展开 SKILL.md 英文原文
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.
帮我安装这个 skill：https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/dev/.agents/skills/work-with-pr/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/dev/.agents/skills/work-with-pr/SKILL.md"# 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