change-delivery-workflow

Runs a local delivery gate covering implementation, testing, documentation, and frozen-head review for repo changes.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill change-delivery-workflow-joey-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-delivery-workflow
Source: https://github.com/Joey-Tools/codex-private-workflows/tree/main/personal_codex/skills/change-delivery-workflow
Command: npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill change-delivery-workflow-joey-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial repository changes often ship without consistent local validation, documentation updates, or an independent review of the exact commit being landed. This Skill enforces a disciplined local gate so every landing commit is implemented, tested, documented, and reviewed before it is accepted or handed off toward PR readiness. ## Core Features & Use Cases - Structured local gate: Walks changes through scope definition, implementation, build and test, documentation updates, landing commit formation, frozen-head review, and acceptance. - Frozen exact-head review: Requires review to run against an immutable base_sha..head_sha range, and invalidates prior results if any post-review commit changes the head. - Clear handoff boundaries: Delegates reviewer adapters, workspace isolation, CI recovery, and PR readiness to the review-orchestration-playbook instead of duplicating that policy. - Use Case: After finishing a feature branch, use this Skill to run the full local validation suite, update project docs, form the signed landing commit, and get that exact head reviewed before pushing. ## Quick Start Run the change delivery workflow on my current branch to validate, document, and review the landing commit before I open a PR.

Frequently Asked Questions about change-delivery-workflow

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

FAQPage Schema
How do I run a local delivery gate before opening a pull request?

Follow the workflow steps: establish scope, implement the change, run the widest relevant build and test validation, update durable documentation, form the landing commit, then review the frozen exact head. Only accept the head_sha that passed every gate.

What is a frozen exact-head review in Git workflows?

It is a review run against an immutable base_sha..head_sha range of committed Git objects rather than a live working tree. Any commit created after the review, including amends or squash operations, invalidates the result and requires revalidation.

Does this workflow handle pushing and PR creation?

No, the local gate stops at the reviewed commit and does not push without separate authorization. Push, PR operations, CI repair, and merge readiness are delegated to the review-orchestration-playbook.

How should long-running tests be handled during the delivery gate?

Long gates can run through a repository-approved background runner such as cbth, keeping them pollable across turns. Persist the source thread and job identifiers and poll for results rather than blocking on synchronous delivery.

What happens if a gate stays inconclusive after recovery attempts?

The workflow stops at an evidence-backed decision point rather than forcing acceptance. It reports every gate that could not run along with its residual risk so the blocker can be resolved explicitly.