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

service-release

Skill188 starsChanged 13 days agoMITView on GitHub

Prepares and validates agent-app-ingestion releases. Use for release branches, VERSION, changelog entries, compatible Agent Landing Zone pins, tags, images, and GitHub Release notes.

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 · 1

    1. Azure/gpt-rag-ingestion★ 188100% 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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    Very specific

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

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

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

    line 8
  2. Very specific:

    Verify branch, VERSION, changelog, Git tag, and GitHub Release title are synchronized.

    line 17
  3. Very specific:

    After merge, create exactly vX.Y.Z for the tag and release title only with explicit human approval.

    line 25
  4. Very specific:

    After the release, recreate the empty Unreleased section separately on develop.

    line 30

≈ “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

Ingestion service release

Read .github/copilot-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 v.
  3. Replace the staged ## [Unreleased] heading with ## [vX.Y.Z] - YYYY-MM-DD; do not add a new Unreleased section on the release branch.
  4. Verify branch, VERSION, changelog, Git tag, and GitHub Release title are synchronized.
  5. Identify the compatible Azure/agent-landing-zone umbrella and component versions and validate the exact ingestion commit or image in that context.
  6. Record Python, frontend, container, and controlled Azure evidence required by the changed behavior.
  7. Confirm documentation status and rollback or roll-forward steps.
  8. Target the release pull request to main.
  9. After merge, create exactly vX.Y.Z for the tag and release title only with explicit human approval.
  10. Re-fetch the release and verify formatting and the absence of private Azure environment or resource-group names.

After the release, recreate the empty Unreleased section separately on develop. Report incompatible contracts, missing validation, or documentation drift as blockers rather than filling gaps by assumption.

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