ceratops-codex-skill-stage-release

Merge task-worktree branches into a local release branch and validate the staged batch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Stage committed Ceratops skill changes into the runtime checkout's local release/* branch to provide a coherent, unpublished snapshot for validation before shipping.

Core Features & Use Cases

  • Stage committed task-worktree branches into the runtime release/* from main, creating a coherent local snapshot.
  • Switch the runtime checkout to the staged release branch and refresh the installed Ceratops skill set.
  • Run the local validation batch to ensure readiness before GitHub shipping.
  • Optionally remove merged branches and worktrees to keep the local workspace clean.

Quick Start

Stage the committed skill branches into the runtime release and validate the staged batch locally.

Frequently Asked Questions about ceratops-codex-skill-stage-release

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

FAQPage Schema
How do I stage committed git-worktree branches into a local release for validation?

Stage committed git-worktree branches into a local release by merging ready task-worktree branches from main into a release/* branch, switching the runtime checkout, and refreshing the installed skill set to create a coherent unpublished snapshot.

What is local release staging for skill branches before GitHub shipping?

Local release staging merges committed Ceratops skill branches into a runtime release/* branch to provide a coherent, unpublished snapshot for running validation batches before pushing changes to GitHub.

Do I need PowerShell and git to automate stage release workflows?

Yes, you need git installed as a dependency and PowerShell to run the dedicated deterministic staging script that manages branch merging, runtime checkout switching, and local skill installation updates.

Can I clean up merged git worktrees after staging a release branch?

Yes, you can optionally remove merged branches and worktrees after staging the release branch to keep your local workspace clean and maintain a coherent validated snapshot before shipping.

How does deterministic staging validate a batch before GitHub shipping?

Deterministic staging applies a PowerShell script to merge branches into a release/* branch, switches the runtime checkout, updates the local install, and runs the validation batch to ensure readiness before GitHub shipping.