pr-merge-workflow

Automate Pull Request creation, CI checks, merging, and cleanup via GitHub CLI.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill pr-merge-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-merge-workflow
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/pr-merge-workflow
Command: npx skills add https://github.com/takemo101/compose-workflow --skill pr-merge-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of creating, monitoring, merging, and cleaning up Pull Requests, ensuring a smooth and efficient development workflow.

Core Features & Use Cases

  • Automated PR Creation: Generates PRs with standardized templates, including issue linking and summary.
  • CI Monitoring: Waits for and verifies CI checks before merging.
  • Smart Merging: Supports various merge strategies (merge, squash, rebase) and handles common errors like worktree conflicts.
  • Post-Merge Cleanup: Automatically closes related issues, updates environment states, and cleans up resources.
  • Rollback Procedures: Provides clear steps for reverting merged changes if critical issues arise.

Quick Start

Execute the full PR merge workflow for pull request number 42, providing environment ID 'abc-123-def' for cleanup.

Frequently Asked Questions about pr-merge-workflow

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

FAQPage Schema
How do I automate the entire pull request lifecycle from creation to merge?

You can automate the complete PR workflow by generating standardized PRs, monitoring CI checks, executing smart merges, and triggering post-merge cleanup automatically. This ensures a smooth and efficient development workflow without manual intervention.

What's the best way to handle worktree conflicts during an automated PR merge?

Smart merging handles common errors like worktree conflicts automatically during the PR merge process. It supports various merge strategies including standard merge, squash, and rebase to ensure successful code integration.

Can I automate environment resource deletion after a GitHub PR is merged?

Yes, post-merge cleanup automatically closes related issues, updates environment states, and deletes environment resources. You simply provide the environment ID when executing the workflow to trigger automated resource cleanup.

How do I wait for CI checks to pass before merging a pull request automatically?

CI monitoring waits for and verifies CI checks before merging a pull request. The automated workflow integrates with GitHub CLI to continuously monitor CI status and only proceeds with merging once all checks pass successfully.

What are the rollback procedures if an automated PR merge introduces critical issues?

The workflow provides clear rollback procedures for reverting merged changes if critical issues arise after an automated PR merge. These steps ensure you can quickly undo merged code and restore the repository to its previous stable state.

Do I need GitHub CLI to automate pull request operations and post-merge cleanup?

Yes, GitHub CLI is required as the workflow integrates with it for all PR operations. This integration enables automated PR creation, CI monitoring, smart merging, and post-merge cleanup including environment resource deletion.