pull-request-shipping

Create a clean branch and structured pull request from a verified milestone.

9|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/calcosmic/Aether --skill pull-request-shipping
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request-shipping
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/colony/pull-request-shipping
Command: npx skills add https://github.com/calcosmic/Aether --skill pull-request-shipping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines turning verified work into a clean, review-ready pull request and a release-ready branch by filtering artifacts and organizing changes for stakeholders.

Core Features & Use Cases

  • PR creation and branch management: Automatically creates a focused PR branch from main/master, filtering colony artifacts and ensuring only relevant changes are shipped.
  • Automated PR body generation and labeling: Generates a structured PR description, applies labels, and notifies reviewers to accelerate approvals.
  • Pre-ship governance and CI integration: Enforces pre-ship checks, triggers CI/CD checks, and posts a colony-summary to the PR for transparency.

Quick Start

Create a PR from a verified milestone to the main branch, filtering artifacts and preparing for review.

Frequently Asked Questions about pull-request-shipping

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

FAQPage Schema
How do I automate GitHub pull request creation from a completed milestone?▼

To automate GitHub pull request creation, this Skill generates a clean branch from main, filters out colony artifacts, and creates a structured PR with labels and reviewer notifications once your milestone is verified and complete.

What is the best way to generate a structured PR body for a release branch?▼

The best way to generate a structured PR body is to use an automated workflow that filters irrelevant artifacts, organizes relevant changes for stakeholders, and posts a colony-summary directly to the PR for transparency.

How do I enforce pre-ship checks and trigger CI integration before opening a PR?▼

You can enforce pre-ship governance by running automated pre-ship checks and triggering CI/CD integration directly within the PR workflow, ensuring the release-ready branch passes validation before review.

Do I need a main branch to automate my git workflow for pull requests?▼

Yes, a main or master branch is required to automate this git workflow, as the Skill creates a focused PR branch directly from main to ensure only relevant changes are shipped for review.

Can I filter artifacts automatically when preparing a pull request for review?▼

Yes, you can filter artifacts automatically during PR preparation by configuring the workflow to exclude colony artifacts, ensuring that only relevant changes are organized into the review-ready pull request.