agentleFS
Sign inStart free
openvinotoolkitopenvinotoolkit/openvino.genai/.github/skills/generate-release-notes/SKILL.md

generate-release-notes

Skill608 starsChanged 34 days agoApache-2.0View on GitHub

Generate OpenVINO GenAI release notes from commits since the latest release. Use when: preparing release notes, summarizing a release branch, or comparing the latest release tag with the current release branch.

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the bundled script from the repository root:

    line 14
  2. Very specific:

    Read the Current release branch reported by the script and remove the upstream/ prefix to get the local release branch name.

    line 22
  3. Distinctive:

    Check out the local release branch:

    line 24
  4. Distinctive:

    If checkout fails for any reason, stop immediately without creating or modifying the release notes.

    line 30
  5. Distinctive:

    If a commit subject does not provide enough information, inspect the currently checked-out release branch's source code, public APIs, …

    line 34
  6. Very specific:

    Create a Markdown file named release_notes_YYYY.N.md with the following template:

    line 46

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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

Generate Release Notes

Generates release notes for openvinotoolkit/openvino.genai from commits added after the latest release tag and writes them to a Markdown file.

Procedure

Step 1: List Release Commits

Run the bundled script from the repository root:

bash .github/skills/generate-release-notes/list_release_commits.sh

Step 2: Check Out the Release Branch

Read the Current release branch reported by the script and remove the upstream/ prefix to get the local release branch name. For example, use releases/2026/4 for upstream/releases/2026/4.

Check out the local release branch:

git checkout <release-branch>

If checkout fails for any reason, stop immediately without creating or modifying the release notes. Ask the user to check out the release branch cleanly, then rerun this skill.

Step 3: Generate Release Notes

If a commit subject does not provide enough information, inspect the currently checked-out release branch's source code, public APIs, tests, bindings, samples, or documentation to prepare an accurate description.

Group commits into categories:

  • Features
  • LLM Bench, WWB Tools
  • JS Bindings
  • Other Changes
  • Docs Updates
  • Discontinued
  • Deprecated

Create a Markdown file named release_notes_YYYY.N.md with the following template:

# OpenVINO™ GenAI Release Notes YYYY.N

## Features

## LLM Bench, WWB Tools

## JS Bindings

## Other Changes

## Docs Updates

## Discontinued

## Deprecated

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.

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