ck-ship-pr

Create pull requests for submodule updates with verified gitlink bumps.

4|Updated Aug 15, 2023
One-click install
npx skills add https://github.com/chainkemists/CkFoundation --skill ck-ship-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck-ship-pr
Source: https://github.com/chainkemists/CkFoundation/tree/main/.claude/skills/ck-ship-pr
Command: npx skills add https://github.com/chainkemists/CkFoundation --skill ck-ship-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of maintaining complex superproject-submodule relationships by enforcing a review-first workflow that prevents direct, unverified pushes to development branches.

Core Features & Use Cases

  • PR-First Publishing: Automates the creation of pull requests for submodules instead of direct pushes, ensuring maintainer oversight.
  • Gitlink Integrity: Manages the critical timing of superproject gitlink bumps to ensure they only point to verified, merged submodule SHAs.
  • Use Case: Use this when working on a multi-repo project where you need to ship feature updates to submodules safely without risking the stability of the shared development branch.

Quick Start

Initiate the ck-ship-pr workflow to publish your current submodule feature branches as pull requests for maintainer review.

Frequently Asked Questions about ck-ship-pr

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

FAQPage Schema
How do I publish submodule updates via pull requests instead of direct commits?

You can publish submodule updates via pull requests by initiating a workflow that creates PRs for submodule feature branches, ensuring maintainer oversight and preventing unverified direct pushes to development branches.

What is the best way to manage superproject gitlink bumps for verified submodule SHAs?

Managing superproject gitlink bumps safely requires a review-gated workflow that times gitlink updates to point only to verified, merged submodule SHAs, preventing broken dependency synchronization across your multi-repo project.

Do I need GitHub CLI integration to enforce review-gated merges for submodules?

Yes, you need GitHub CLI integration to enforce review-gated merges for submodules, along with strict adherence to the established pre-flight and rebase procedures defined in the foundation workflow.

How does a review-first pull request workflow prevent unverified pushes to development branches?

A review-first pull request workflow prevents unverified pushes by automating PR creation for submodules and enforcing maintainer oversight, blocking direct commits to shared development branches.

When should I use a PR-based workflow for shipping feature updates to submodules?

You should use a PR-based workflow for shipping submodule feature updates when working on multi-repo projects where dependency synchronization and branch stability require controlled, review-gated merges.

What are the limitations of shipping submodule updates without review-gated pull requests?

Shipping submodule updates without review-gated pull requests risks unverified pushes to development branches, broken dependency synchronization, and superproject gitlinks pointing to unmerged or unstable submodule SHAs.