pr-complete

Verify GitHub PR readiness by checking approvals, CI status, mergeability, and notify humans via bus message.

4|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/mkalkere/agent-coordinator --skill pr-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-complete
Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/development/pr-complete
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill pr-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often stall after code review when a merge requires human decision. This skill automates the verification that a PR is ready to merge and notifies the right person to take action, reducing wait times and confusion.

Core Features & Use Cases

  • Verify PR readiness: checks that PR is approved, CI checks pass, there are no merge conflicts, and review comments are resolved.
  • Notify humans: publishes a bus message with task_id and PR number, and can post an optional PR comment to surface status.
  • Maintain workflow state: keeps the task in approved status until a human merges and updates the dashboard.
  • Standalone compatibility: supports operation without the coordinator URL.

Quick Start

Trigger this skill after a PR is approved to verify readiness and notify a human to perform the merge.

Frequently Asked Questions about pr-complete

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

FAQPage Schema
How do I automate pull request readiness checks before notifying a human to merge?

The skill verifies pull request readiness by checking approvals, CI status, mergeability, and resolved review comments, ensuring the PR is fully approved before notifying a human to perform the merge.

What is the best way to notify reviewers when a GitHub pull request is ready to merge?

The best way to notify reviewers is to publish a bus notification containing the task_id and PR number, with an optional PR comment, surfacing the merge-ready status to the right human for action.

Does this pull request workflow automation automatically merge branches when CI passes?

No, this pull request workflow automation never performs automated merges. It maintains the task in an approved state and strictly coordinates human handoffs for the final merge decision and execution.

How do I track an approved pull request task state until a human merges the code?

The skill tracks the approved pull request task state by keeping it in approved status and updating the dashboard until a human executes the manual merge.

Can I verify pull request mergeability without a coordinator URL in my workflow?

Yes, you can verify pull request mergeability without a coordinator URL. The skill supports standalone compatibility, allowing it to operate independently to check CI status and approvals.