ship-to-prod

Open a formatted release pull request into main with Linear references.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/connectedxm/admin-sdk --skill ship-to-prod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-to-prod
Source: https://github.com/connectedxm/admin-sdk/tree/main/.claude/skills/ship-to-prod
Command: npx skills add https://github.com/connectedxm/admin-sdk --skill ship-to-prod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and manual effort of opening release PRs by automating the repo-specific conventions required for a correct production-targeted merge. It ensures the PR targets the right main base, includes the correct Linear references harvested from commits and sub-PRs, and satisfies CI gates like version bumping and linear-check requirements.

Core Features & Use Cases

  • Automated release PR creation into main: Resolves the correct head/source branch from the user prompt or your current checkout and prepares a draft for review.
  • Linear Issues harvesting with CI guardrails: Extracts ENG-#### references from commit bodies and referenced PRs to match the repo’s required formatting.
  • Template-accurate PR content and reviewers: Generates a title and body matching the pull request template, and selects reviewers from GitHub collaborators with push access (excluding the author), then requests confirmation before creating.

Quick Start

Ask: "Ship this branch to prod by opening a release PR into main. Use my current branch as the head, draft the PR first, and wait for my confirmation before creating it."

Frequently Asked Questions about ship-to-prod

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

FAQPage Schema
How do I automate opening a release pull request into main with Linear references?

To automate opening a release pull request into main, this Skill resolves the head branch and extracts ENG-#### ticket references from commit bodies and sub-PRs. It formats the PR title, body, and reviewers to satisfy CI linear-check and version-check requirements before requesting user confirmation.

Why does my version bump validation fail when cutting a release PR to main?

Version bump validation fails when the release PR lacks required Linear references or an appropriate version increment against main. This Skill enforces version bump validation by extracting ENG-#### references from commit bodies and referenced PRs to satisfy CI gate checks.

Does this release management workflow support GitHub and Linear integration?

Yes, this release management workflow supports GitHub and Linear integration by harvesting ENG-#### ticket references from commit bodies and sub-PRs. It selects reviewers from GitHub collaborators with push access while ensuring the PR targets the correct main base branch.

How to generate a production release PR draft from a named branch for review?

To generate a production release PR draft from a named branch, this Skill resolves the source branch from your prompt or current checkout and prepares a template-accurate PR body. It identifies reviewers with push access and waits for your confirmation before creating the PR.

What is the best way to ensure CI validation passes for npm publishing and version bumps?

The best way to ensure CI validation passes for npm publishing and version bumps is to automate the extraction of ENG-#### references and validate the version bump against main. This Skill applies repo-specific conventions to prevent CI gate failures before creating the release PR.