agentleFS
Sign inStart free
DusttooDusttoo/orka/skills/release-integration/SKILL.md

release-integration

Skill2 starsChanged 46 days agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. public-ui/kolibri★ 290same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the repository's schema-versioned workflow configuration.

    line 8
  2. Very specific:

    Run orchestration-engine.py validate-config.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Run orchestration-engine.py validate-config. Stop before mutation on any unsupported schema version, undefined branch role, invalid transition, missing adapter, or incomplete guard.
  2. Determine the requested transition and candidate identity from the user or the repository's current release state.
  3. Run:
    orchestration-engine.py adapter-plan --host codex <transition> \
  --var candidate_id=<id>
    The output is authoritative for branch roles, evidence, approvals, CI categories, environment roles, artifact identity, tags, reconciliation, and cleanup.
  4. 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.
  5. Execute the transition through:
    orchestration-engine.py transition <candidate-id> <transition> \
  --evidence <name>=<path> \
  --ci <category>=green \
  --candidate-sha <sha> \
  --artifact-id <artifact> \
  --tag <tag>
    Pass only arguments required by the configured plan.
  6. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free