mcpbeat

Service Release

azure/service-release

Prepares and validates gpt-rag-ingestion releases. Use for release branches, VERSION, changelog entries, compatible GPT-RAG pins, tags, images, and GitHub Release notes.

377 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
186
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Azure/gpt-rag-ingestion --skill service-release

The instruction itself

1 sections, as written by the author

Ingestion service release

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

artifact.

  • Determine the intended semantic version and create release/x.y.z from

develop.

  • Set root VERSION to x.y.z without v.
  • Replace the staged ## [Unreleased] heading with

## [vX.Y.Z] - YYYY-MM-DD; do not add a new Unreleased section on the

release branch.

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

synchronized.

  • Identify the compatible Azure/GPT-RAG umbrella and component versions and

validate the exact ingestion commit or image in that context.

  • Record Python, frontend, container, and controlled Azure evidence required

by the changed behavior.

  • Confirm documentation status and rollback or roll-forward steps.
  • Target the release pull request to main.
  • 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.

How to use it

Copy the folder

Take azure/service-release from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.