pdd-pr-merge

Merge reviewed GitHub PRs and trigger archival workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically merges PRs that are reviewed and ready for delivery and triggers the archival workflow, reducing manual steps and human error.

Core Features & Use Cases

  • GitHub 模式与本地模式支持:适用于 GitHub 工作流和本地开发环境。
  • 前置检查与合并策略:确保 PR 状态、权限和阻塞问题,并支持 squash 与合并等策略。
  • 归档与报告生成:合并完成后触发归档、更新状态并生成合并报告。
  • 输入输出与协作:接受 Change ID 或 PR 编号作为输入,并对对应变更执行归档。

Quick Start

Use the Change ID or PR number to initiate the merge and archival workflow.

Frequently Asked Questions about pdd-pr-merge

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

FAQPage Schema
How do I automate a safe pull-request merge and trigger archival on GitHub?

To automate a safe pull-request merge, this Skill applies pre-checks for status and permissions, supports squash or merge strategies, and triggers OpenSpec changes archival upon completion.

What is the best way to merge reviewed PRs ready for delivery using a Change ID?

Merging reviewed PRs via a Change ID is handled by automating the merge workflow, verifying blocking issues, executing the merge, and generating a final merge report for archival.

Can I use squash and merge strategies for local development environments?

Yes, you can use squash and merge strategies for local development environments, as the workflow supports both GitHub-based workflows and local mode alongside multiple merge strategies.

Does the PR merge workflow perform pre-checks before triggering archival?

The PR merge workflow performs pre-checks before triggering archival by verifying PR status, user permissions, and any blocking issues to ensure safe delivery.

What happens to OpenSpec changes after a GitHub pull-request merge is completed?

After a GitHub pull-request merge is completed, the workflow triggers OpenSpec changes archival, updates the delivery status, and generates a comprehensive merge report.

Are there limitations when automating PR archival for local development workflows?

Limitations for automating PR archival involve requiring a valid Change ID or PR number, and the process strictly depends on successful pre-checks before executing the merge and subsequent archival.