agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/gpt-rag-ui/.github/skills/component-release/SKILL.md

component-release

Skill10 starsChanged 12 days agoMITView on GitHub

Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 1

    1. Azure/agent-app-ui★ 10100% same

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Azure/agent-app-mcp★ 22same name
    2. Azure/gpt-rag-mcp★ 22same 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 repository6 other files it gives its agents.

The file

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:

    Start from the current develop branch and create release/X.Y.Z.

    line 8
  2. Very specific:

    Verify the branch name, VERSION, changelog heading, proposed tag vX.Y.Z, and release title describe the same version.

    line 15
  3. Distinctive:

    Run the complete existing test suite and any auth, accessibility, deployment, or cross-repository validation required by the changes.

    line 17
  4. Distinctive:

    After merge and explicit human approval, create the tag and release using the validated commit.

    line 21
  5. Very specific:

    After merge, synchronize the released version and changelog to develop through a separate feature pull request.

    line 24
  6. Distinctive:

    Do not introduce unrelated feature work on a release branch.

    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

Agent Landing Zone UI component release

  1. Start from the current develop branch and create release/X.Y.Z.
  2. Choose a semantic version from the shipped change set. Do not change VERSION on develop merely to anticipate a release.
  3. Set root VERSION to X.Y.Z without a v prefix.
  4. Convert the accumulated ## [Unreleased] section into ## [vX.Y.Z] - YYYY-MM-DD. Do not retain Unreleased on a release branch or main.
  5. Verify the branch name, VERSION, changelog heading, proposed tag vX.Y.Z, and release title describe the same version.
  6. Run the complete existing test suite and any auth, accessibility, deployment, or cross-repository validation required by the changes.
  7. Confirm documentation, migration, compatibility, and rollback status.
  8. Open the release pull request from release/X.Y.Z to main.
  9. After merge and explicit human approval, create the tag and release using the validated commit. Publishing images or deploying production requires separate explicit approval.
  10. After merge, synchronize the released version and changelog to develop through a separate feature pull request. Restore exactly one empty ## [Unreleased] section on develop only, without bypassing protection.
  11. Record the release artifacts, evidence, compatibility assumptions, and rollback path in the handoff.

Do not introduce unrelated feature work on a release branch. Never include credentials, personal data, private environment names, tenant or subscription identifiers, or internal endpoints in release artifacts.

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