ceratops-gh-codex-skill-ship

Ship staged Ceratops skill batches from runtime checkout to GitHub and restore main.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ceratops-code/codex-skills --skill ceratops-gh-codex-skill-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ceratops-gh-codex-skill-ship
Source: https://github.com/ceratops-code/codex-skills/tree/main/skills/ceratops-gh-codex-skill-ship
Command: npx skills add https://github.com/ceratops-code/codex-skills --skill ceratops-gh-codex-skill-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ship staged Ceratops skill batches from the runtime checkout to GitHub and back to the installed runtime on main. This workflow ensures staged changes are validated, shipped, and reconciled with the runtime state to keep deployments consistent.

Core Features & Use Cases

  • Ship staged skill batches from the runtime checkout through GitHub, including PR creation and merge, while preserving the runtime's state.
  • Validate changed skill folders, ensure SKILL.md and agents/config files stay aligned, and reinstall or repair installed junctions after shipping.
  • Use cases include staging new or updated Ceratops skills and returning the runtime to a clean main state after successful shipping.

Quick Start

Ship the staged skill batch from the runtime checkout to GitHub and then restore the runtime main with updated installed skills.

Frequently Asked Questions about ceratops-gh-codex-skill-ship

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

FAQPage Schema
How do I ship staged skill changes from a release branch to GitHub and main?

To ship staged skill changes, this skill validates changed folders in a release/* branch, creates and merges a GitHub PR, then restores the runtime checkout to main while reinstalling updated skills.

What does the skill shipping workflow do when SKILL.md and agents/openai.yaml are misaligned?

The shipping workflow enforces alignment between SKILL.md and agents/openai.yaml during validation, preventing misconfigured skill folders from being shipped to GitHub and the installed runtime.

Do I need to reinstall the runtime after merging skill changes to main?

Yes, the workflow automatically re-runs the runtime installer after shipping to synchronize installed skills and repair junctions, ensuring the local main checkout reflects the merged changes.

Can I use this workflow to validate staged skill folders before creating a pull request?

Yes, validating changed skill folders is a core step of the workflow that occurs before GitHub PR creation, ensuring only properly configured skills proceed to the ship and merge stage.

Why does the runtime need to return to main after shipping skill batches to GitHub?

Returning the runtime to main after shipping reconciles the local checkout state with the merged remote changes, keeping deployments consistent and restoring a clean working branch.

What happens if installed skill junctions break after a GitHub merge?

The workflow repairs broken installed junctions by re-running the runtime installer after the merge, synchronizing installed skills with the updated main branch state.