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

component-release

Skill22 starsChanged 3 months agoMITView on GitHub

Prepares and validates GPT-RAG MCP component releases. Use for versions, dependency locks, changelog entries, release branches, tags, GitHub Releases, and platform pin coordination.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

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

    line 8
  2. Very specific:

    Add ## [vX.Y.Z] - YYYY-MM-DD to CHANGELOG.md with accurate Keep a Changelog categories.

    line 16
  3. Very specific:

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

    line 24
  4. Distinctive:

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

    line 30

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

GPT-RAG MCP component release

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

  1. Determine the semantic version and create release/x.y.z from current main.
  2. Set VERSION and project.version in pyproject.toml to X.Y.Z.
  3. Regenerate uv.lock from the exact committed project metadata and inspect dependency changes.
  4. Add ## [vX.Y.Z] - YYYY-MM-DD to CHANGELOG.md with accurate Keep a Changelog categories.
  5. Validate the exact release commit with the narrowest existing checks, startup or Inspector behavior as applicable, and a container build when dependency or packaging risk requires it.
  6. Confirm whether Azure/GPT-RAG must update its MCP component pin and link the coordinated change.
  7. Target the release pull request to main.
  8. Use exactly vX.Y.Z for the Git tag and GitHub Release title.
  9. Review release notes for secrets, personal data, and private Azure validation environment or resource-group names.
  10. Re-fetch the published release and verify title, tag, body formatting, and target commit.

Do not publish a tag, release, package, image, or production deployment without explicit human approval. Report missing validation or incompatible platform pins as blockers rather than filling gaps by assumption.

Download now (ZIP)

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Azure/agent-app-ui★ 10same name
    2. Azure/gpt-rag-ui★ 10same 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.

Does it work?

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

Reviews can't be read right now.

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