work-with-pr

Coordinate a complete PR lifecycle from worktree setup to merge with CI verification.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/HaydernCenterpoint/Codex-Skills --skill work-with-pr-hayderncenterpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-with-pr
Source: https://github.com/HaydernCenterpoint/Codex-Skills/tree/main/skills/work-with-pr
Command: npx skills add https://github.com/HaydernCenterpoint/Codex-Skills --skill work-with-pr-hayderncenterpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and automate a complete PR lifecycle from isolated worktree setup to PR merge, including atomic commits and CI-driven verification.

Core Features & Use Cases

  • Phase-based workflow: setup, implement, PR creation, verification (CI + review-work + Cubic), merge, and cleanup.
  • Failure recovery and safe cleanup: isolates work in a worktree to avoid polluting the main repo, with automated re-run loops on failures.
  • Iterative gate-driven validation: CI checks, multi-agent code review, and automated cubic approval drive PR readiness.

Quick Start

Invoke this skill to manage a full PR lifecycle from a dedicated worktree through PR creation, verification, and merge.

Frequently Asked Questions about work-with-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the entire PR lifecycle from commit to merge?

You can automate the full PR lifecycle by using a phase-based workflow that sets up an isolated git worktree, makes atomic commits, creates the PR, and iterates through CI checks and code review until all gates pass before merging.

What is the safest way to isolate PR work before running automated CI checks?

Isolating PR work in a dedicated git worktree prevents pollution of your main repository, keeping local state clean and enabling safe, repeatable PR delivery across CI and code review gates.

How do I handle PR verification failures during automated merge workflows?

PR verification failures trigger automated re-run loops within the workflow, guiding phase-based failure recovery and iterating CI checks and multi-agent code review until the PR passes all safety gates.

Can I enforce a deterministic commit strategy during PR automation?

Yes, this PR automation enforces a deterministic commit strategy by structuring implementation into atomic commits within an isolated worktree, ensuring clean, repeatable, and verifiable code delivery.

What is the best way to structure a workflow for CI-driven PR verification?

The best approach is a phase-based workflow that separates setup, implementation, PR creation, verification, merge, and cleanup, driving PR readiness through iterative gate validation rather than manual checks.

When should I avoid using worktree isolation for PR automation?

You should avoid worktree isolation if your development workflow does not require safe, repeatable PR delivery or if your CI environment lacks support for isolated git worktree setup and phase-based failure recovery.