Lifecycle phasesv0.1.1

auto-ship

Turns verified work into release-ready artifacts while keeping failed, skipped, and irreversible gates honest.

WORKFLOW / 05/auto-ship [what to ship — a branch/feature] (default: the current branch)
  1. 01

    Pin the release scope and adversarially gate the ready claim.

  2. 02

    Run final validation, review, security, observability, and rollback checks.

  3. 03

    Prepare atomic commits, grounded release notes, version, and user-facing docs.

  4. 04

    Open the pull request or stage a flagged rollout.

  5. 05

    Stop for explicit approval before any irreversible trigger.

operating envelope

Use it deliberately.

The shortest useful definition of where this skill helps—and where it should stay out of the way.

Use when

  • A built, tested, and reviewed change is ready for release preparation.
  • The branch needs grounded notes, versioning, documentation, and a pull request.
  • A risky rollout needs flags, monitoring, and a rollback path before launch.

Do not use when

  • Implementation or review is still incomplete.
  • A configured release gate is red or did not run.
  • You expect an irreversible deploy or publication without fresh human approval.

output contract

What must be true when it stops.

Produces

  • Truthful pre-launch gate matrix
  • Grounded version, changelog, release notes, and documentation
  • Pull request or staged-rollout plan
  • Rollback path and explicit-approval ledger

Guarantees

  • Every configured gate must actually run and pass.
  • The final validation runs on the integrated release state.
  • Release notes describe only observed changes.
  • Risky rollout paths include monitoring and rollback before launch.
  • Unsafe force-push and ref-deletion patterns are blocked by the bundled guard.
  • Deploy, publication, and destructive migration triggers remain human-owned.

Honest failure states

  • blocked_gate — a configured gate failed or did not run
  • awaiting_approval — an irreversible release action is ready but not authorized
  • no_rollback — the proposed rollout lacks a safe back-out path
  • validation_red — the integrated release state is not green

enforcement

Know which claims are executable.

Scripts are linked when this skill owns deterministic machinery. The remaining rules are explicit operating contracts and must not be marketed as hooks.

install and invoke

One skill, three honest surfaces.

skills.sh

Available

Universal skill installation, including Claude Code and Codex.

npx skills add https://github.com/ulpi-io/skills-autonomous-engineering --skill auto-ship

Claude Code plugin

Available

Install the full plugin, then invoke /auto-ship or let routing select it from context.

Claude installation →

Codex plugin

Work in progress

A work in progress on the codex-native-plugin branch — build it, start a new session, then invoke $autonomous-engineering:auto-ship.

Codex installation →