work-with-pr

Automate the pull request lifecycle by decomposing complex tasks into small, independently mergeable PRs, managing isolated git worktrees, and enforcing multi-gate verification. This ensures high-quality, atomic code delivery without manual intervention.

Splitting complex features into independently mergeable PRs is achieved through atomic PR decomposition. This approach automatically breaks down tasks into isolated worktrees, improving review quality and ensuring each code delivery is production-ready.

Yes, you need the GitHub CLI to automate branch creation, PR submission, and auto-merge operations. A configured development environment is also required to execute the end-to-end pull request lifecycle and integrate with automated CI.

Evidence-based verification for pull requests enforces a strict loop of manual QA and automated checks. This multi-gate verification process ensures every PR meets production-ready standards before integration with CI and bots.

Yes, you can use isolated git worktrees to manage parallel development and prevent context switching. This approach avoids environment pollution by maintaining separate working directories for each atomic task within the full PR lifecycle.

Avoid automating pull request management when tasks cannot be decomposed into atomic commits or when manual QA evidence and automated CI checks are not required. The workflow depends heavily on isolated worktrees and multi-gate verification to ensure production readiness.