pr-workflow

Route pull request tasks to matching lifecycle workflows with evidence-based PR bodies.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill pr-workflow-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/process/pr-workflow
Command: npx skills add https://github.com/notque/vexjoy-agent --skill pr-workflow-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I create a pull request with an evidence-driven review flow?

To create a pull request with an evidence-driven review flow, you route the request through a task-aware lifecycle that enforces CI status checks and a mandatory Summary, Changes, and Notes body structure for gh pr create.

What is PR mining and how does it extract review knowledge?

PR mining is the process of extracting review knowledge from past pull requests, allowing you to route and execute operational procedures that capture historical feedback and apply it to current code review workflows.

How do I fix PR comments and sync branches during a git workflow?

You fix PR comments and sync branches by routing the exact PR task request to dedicated reference instructions, which execute the correct lifecycle workflow for applying fixes and synchronizing branch states.

Can I automate branch naming validation and commit preparation together?

Yes, you can automate branch naming validation and commit preparation together by using dedicated references that align branch naming conventions with conventional-commit-style workflows for your pull requests.

Does this PR automation approach work without relying on assertions?

Yes, this PR automation approach works by requiring CI and test evidence rather than assertions, aligning with a methodology where gates require evidence before proceeding with pull request operations.

Why does my pull request creation skip the CI status check lifecycle?

Your pull request creation skips the CI status check lifecycle when task-aware routing is not applied, which this workflow prevents by mapping exact PR operations to the correct operational procedures and references.