What problem does it solve?
It prevents “commit my changes” workflows from skipping the PR lifecycle steps (review, CI status checks, fixes, cleanup, and knowledge extraction) and routes the agent to the correct operational procedure based on the exact PR task the user requests.
Core Features & Use Cases
- Evidence-driven PR operations: Supports PR actions that rely on CI/test evidence rather than assertions, aligning with the toolkit’s “gates require evidence” methodology.
- Task-aware routing for the full PR lifecycle: Routes to the correct reference for sync, pipeline creation, fixes for review comments, CI/status checks, cleanup after merge, feedback processing, PR mining, branch naming/validation, commits, and Codex-based code review.
- Mandatory PR-body structure for created PRs: Enforces a consistent Summary → Changes → Notes format for
gh pr create --body to bypass the GitHub template.
- Branch-name and commit-intent aligned workflows: Uses dedicated references for branch naming conventions and for conventional-commit-style commit/PR preparation.
Quick Start
Use the pr-workflow skill to create and manage a pull request by saying: /pr-workflow create PR and sync my changes for review.