pr-captain-land

Merge agent branches into main with version bumps and CI verification.

39|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/the-agency-ai/the-agency --skill pr-captain-land
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-captain-land
Source: https://github.com/the-agency-ai/the-agency/tree/main/.claude/skills/pr-captain-land
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill pr-captain-land

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex process of landing an agent's prepared branch as a GitHub pull request with version management and CI verification, reducing manual coordination errors.

Core Features & Use Cases

  • Automatic PR Creation and Version Bump: Safely advances agency versions and creates release PRs after validation.
  • CI Monitoring: Checks and waits for successful test results before merging, ensuring code quality.
  • Stakeholder Notification: Dispatches updates to agents and teams upon successful landing and release.

Quick Start

Use the pr-captain-land skill to land an agent's branch, verifying CI success, merging the PR, and creating a release, all in an automated orchestration.

Frequently Asked Questions about pr-captain-land

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

FAQPage Schema
How do I automate GitHub pull request creation and version bumping for agent branches?

Automating GitHub pull request creation and version bumping is handled by validating agent branches, advancing agency versions, and generating release PRs automatically. This orchestration reduces manual coordination errors during synchronized landings.

What is the best way to verify CI success before merging a pull request?

The best way to verify CI success before merging is to use automated CI monitoring that actively checks and waits for successful test results. This ensures code quality is validated before the branch lands in the main branch.

How does release automation handle failure recovery when merging branches to main?

Release automation handles failure recovery by coordinating branch merges to main through safety checks and structured protocols. If checks fail, the process pauses to prevent broken code from landing and triggering a release.

Can I automate stakeholder notifications after a successful pull request merge and release?

Yes, you can automate stakeholder notifications after a successful pull request merge and release. The process dispatches automated updates to agents and teams once the branch lands and the version release completes successfully.

Do I need external dependencies to automate pull request merging and version management?

No external dependencies are required to automate pull request merging and version management. The skill operates independently using its internal scripts and assets to coordinate the entire landing process safely.