pdd-pr-batch

Batch merge multiple OpenSpec Changes into a single pull request.

13|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-pr-batch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pdd-pr-batch
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/pr/pdd-pr-batch
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-pr-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch merging multiple OpenSpec Changes into a single PR enables releasing related improvements together, reducing review overhead and ensuring coherent deployment.

Core Features & Use Cases

  • Batch merge: combine multiple Changes into a single PR for streamlined release.
  • Validation & review: verify Change existence, branch creation, and conflict handling, with unified review.
  • Use cases: release of multiple small fixes, coordinated feature upgrades, and bulk configuration or documentation updates.

Quick Start

Provide Change IDs to batch into a single PR and run the batch PR command to create the unified PR.

Frequently Asked Questions about pdd-pr-batch

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

FAQPage Schema
How do I batch merge multiple changes into a single pull request?▼

Batch merge multiple changes into a single pull request by providing Change IDs to enforce validation, branch creation, conflict resolution, and unified review before creating the PR.

Why should I combine multiple small fixes into one pull request for release?▼

Combining multiple small fixes into one pull request reduces review overhead and ensures coherent deployment by releasing related improvements together.

What is the best way to handle conflict resolution during a batch PR creation?▼

Batch PR creation handles conflict resolution by verifying Change existence and branch creation, enforcing validation workflows to manage conflicts before merging into the unified PR.

Can I merge coordinated feature upgrades and configuration updates together in a batch review?▼

Yes, you can merge coordinated feature upgrades and bulk configuration updates into a batch review workflow, validating multiple OpenSpec Changes to streamline unified release.

Do I need to provide Change IDs to start a batch merge workflow?▼

Yes, you need to provide Change IDs as input to run the batch PR command, which validates the changes and creates a unified pull request for streamlined release.