agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/agent-app-orchestrator/.github/skills/orchestrator-release/SKILL.md

orchestrator-release

Skill107 starsChanged 3 days agoMITView on GitHub

Prepares and validates Agent Landing Zone Orchestrator releases. Use for VERSION, changelog entries, release branches, tags, GitHub Release notes, and synchronized develop follow-up.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Verify the branch, VERSION, changelog, intended tag, and GitHub Release title are synchronized, accounting for their required prefix …

    line 18
  2. Distinctive:

    Keep only release preparation on the branch and target the pull request to main.

    line 20
  3. Distinctive:

    Keep changelog, release notes, and published operator documentation consistent and free of secrets or private Azure environment names.

    line 24
  4. Very specific:

    Use exactly vX.Y.Z for both the Git tag and GitHub Release title.

    line 26
  5. Very specific:

    After pushing the release branch, restore one empty [Unreleased] section at the top of develop, commit it, and push develop.

    line 27
  6. Distinctive:

    Do not publish a tag, release, package, image, or production deployment without explicit human approval.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Agent Landing Zone Orchestrator release

Read .github/copilot-instructions.md and .github/instructions/release.instructions.md completely before changing a release artifact.

  1. Determine the intended semantic version and create release/X.Y.Z from develop.
  2. Set root VERSION to X.Y.Z without a v prefix.
  3. Replace the single [Unreleased] heading with ## [vX.Y.Z] - YYYY-MM-DD; do not leave [Unreleased] on the release branch.
  4. Verify the branch, VERSION, changelog, intended tag, and GitHub Release title are synchronized, accounting for their required prefix differences.
  5. Keep only release preparation on the branch and target the pull request to main.
  6. Validate the exact commit with the relevant pytest, frontend, deployment, contract, and Copilot asset checks.
  7. Keep changelog, release notes, and published operator documentation consistent and free of secrets or private Azure environment names.
  8. Use exactly vX.Y.Z for both the Git tag and GitHub Release title.
  9. After pushing the release branch, restore one empty [Unreleased] section at the top of develop, commit it, and push develop.
  10. Re-fetch published release notes and verify headings, lists, tables, and sanitized content.

Do not publish a tag, release, package, image, or production deployment without explicit human approval. Report failed validation or version drift as a blocker rather than filling gaps by assumption.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. Azure/gpt-rag-orchestrator★ 107100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository6 other files it gives its agents.

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