Release integration
Skill Dusttoo/claude-orchestrator/skills/release-integration
Advance a configured release or candidate workflow through the shared orchestration engine. The skill name is retained for compatibility; release policy comes from repository configuration, not from this skill.From its SKILL.md
npx -y skills add Dusttoo/claude-orchestrator --skill release-integrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, as published. Nobody here has run it
Advance a configured release workflow
Use the repository's schema-versioned workflow configuration. This skill is the
natural-language entry point for the same behavior exposed by the Claude
/release command. Do not independently implement release policy here.
Plugin paths
Resolve these paths from this skill file before executing them:
../../scripts/orchestration-engine.py../../scripts/merge-guard.sh../../scripts/merge-on-green.sh../../scripts/run-verification.sh
Execute scripts by absolute path while keeping the target repository as the working directory.
Procedure
- Run
orchestration-engine.py validate-config. Stop before mutation on any unsupported schema version, undefined branch role, invalid transition, missing adapter, or incomplete guard. - Determine the requested transition and candidate identity from the user or the repository's current release state.
- Run:
The output is authoritative for branch roles, evidence, approvals, CI categories, environment roles, artifact identity, tags, reconciliation, and cleanup.orchestration-engine.py adapter-plan --host codex <transition> \ --var candidate_id=<id> - Collect each configured evidence item and approval record. Approval must be a separate verifiable record, created by the engine or by a configured external adapter; never treat a free-form state edit as approval.
- Execute the transition through:
Pass only arguments required by the configured plan.orchestration-engine.py transition <candidate-id> <transition> \ --evidence <name>=<path> \ --ci <category>=green \ --candidate-sha <sha> \ --artifact-id <artifact> \ --tag <tag> - For legacy configs without
schema_version: 2, do not invent candidate states. Continue using the repository's existing release process or migrate to a schema-versioned workflow before using release-candidate transitions.
Report the transition, final state, candidate identity, artifact identity, approval records, evidence paths, and any configured reconciliation or cleanup work that remains.