pr-submit

Validate worktree state and dispatch structured PR readiness messages to captains.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process for agents to notify captains when their code branches are ready for pull request review, thereby reducing manual coordination and ensuring consistency in PR workflows.

Core Features & Use Cases

  • Preflight Validation: Checks that the agent operates within a clean, pushed worktree with matching receipt files, preventing errors in PR submissions.
  • Structured Dispatching: Generates and sends a detailed payload to the captain, including branch info, diff hash, receipt path, and scope summary.
  • Use Case: A developer completes feature work in an agent worktree and triggers this Skill to initiate a formal PR request for review, owner-ship, and release process.

Quick Start

To submit your branch for PR review, run /pr-submit --scope "Describe your change".

Frequently Asked Questions about pr-submit

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

FAQPage Schema
How do I automate pull request submissions from an agent worktree?

Automating pull request submissions from an agent worktree involves verifying the worktree state, computing change hashes, and dispatching a structured message with branch info and scope summary to a captain for coordinated review.

What is agent-led pull request dispatching and when do I need it?

Agent-led pull request dispatching is the process of agents notifying captains when code branches are ready for review. You need it to reduce manual coordination and ensure consistency in automated PR workflows.

How do I signal that my Git branch is ready for PR review?

To signal that your Git branch is ready for PR review, run the submission command with a scope description. This triggers preflight validation to ensure a clean, pushed worktree before dispatching the formal PR request.

Does PR submission require a clean worktree before dispatching?

Yes, PR submission requires a clean worktree. Preflight validation checks that the agent operates within a pushed worktree with matching receipt files, preventing errors and ensuring reliability before dispatching the PR payload.

What is included in the structured dispatch payload for a pull request?

The structured dispatch payload for a pull request includes branch information, the computed diff hash, the receipt path, and a scope summary. This ensures captains receive detailed context for coordinated PR management.

Why do I need hash verification for automated pull request workflows?

Hash verification for automated pull request workflows computes a diff hash to confirm worktree state integrity. This increases reliability by ensuring the dispatched PR payload accurately represents the committed changes.