Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Generate release notes for addon packages (non-SDK inference addons, decoder, OCR).
Install Qv Addon Release Notes
$ npx skills add tetherto/qvac --skill qv-addon-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tetherto/qvac qv-addon-release-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/qv-addon-release-notes .claude/skills/qv-addon-release-notes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "qv-addon-release-notes" agent skill from https://github.com/tetherto/qvac/tree/main/.agents/skills/qv-addon-release-notes into .claude/skills/qv-addon-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qv-addon-release-notes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tetherto/qvac/tree/main/.agents/skills/qv-addon-release-notesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tetherto/qvac --skill qv-addon-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tetherto/qvac qv-addon-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/qv-addon-release-notes .agents/skills/qv-addon-release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qv-addon-release-notes" agent skill from https://github.com/tetherto/qvac/tree/main/.agents/skills/qv-addon-release-notes into .agents/skills/qv-addon-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qv-addon-release-notes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tetherto/qvac --skill qv-addon-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tetherto/qvac qv-addon-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/qv-addon-release-notes .cursor/skills/qv-addon-release-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "qv-addon-release-notes" agent skill from https://github.com/tetherto/qvac/tree/main/.agents/skills/qv-addon-release-notes into .cursor/skills/qv-addon-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qv-addon-release-notes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tetherto/qvac.git --path .agents/skills/qv-addon-release-notes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tetherto/qvac --skill qv-addon-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tetherto/qvac qv-addon-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/qv-addon-release-notes .gemini/skills/qv-addon-release-notes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "qv-addon-release-notes" agent skill from https://github.com/tetherto/qvac/tree/main/.agents/skills/qv-addon-release-notes into .gemini/skills/qv-addon-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qv-addon-release-notes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tetherto/qvac qv-addon-release-notesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tetherto/qvac --skill qv-addon-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/qv-addon-release-notes .github/skills/qv-addon-release-notes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "qv-addon-release-notes" agent skill from https://github.com/tetherto/qvac/tree/main/.agents/skills/qv-addon-release-notes into .github/skills/qv-addon-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qv-addon-release-notes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tetherto/qvac --skill qv-addon-release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tetherto/qvac qv-addon-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/qv-addon-release-notes .opencode/skills/qv-addon-release-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "qv-addon-release-notes" agent skill from https://github.com/tetherto/qvac/tree/main/.agents/skills/qv-addon-release-notes into .opencode/skills/qv-addon-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qv-addon-release-notes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
qv-addon-release-notes- GitHub stars
- 674
- Token cost
- ~1.2k tokens
- SKILL.md length
- 510 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Generate release notes for addon packages (non-SDK inference addons, decoder, OCR).
- Works in 3 steps: Identify version and changes (mandatory… → Collect PRs included in this release → Generate Release Notes file
- Preparing release notes
- SKILL.md covers What, When to Use and Instructions
- Calls gh
What it does
Qv Addon Release Notes is an agent skill from tetherto/qvac. Generate release notes for addon packages (non-SDK inference addons, decoder, OCR). Use when preparing release notes or user asks to "generate release notes" for an addon package.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. It works with npm. The repository describes itself as: Open-source local AI SDK - run AI on-device with no cloud, no API keys. Supports GGUF, RAG, image, music, and video generation, speech-to-text, P2P inference, and more… The licence is Apache-2.0.
When your agent uses it
- Preparing release notes
- User asks to generate release notes for an addon package
Example prompts
- “generate release notes”
- “/qv-addon-release-notes”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit d92f697. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Qv Addon Release Notes loads about 1.2k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 510 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tetherto/qvac at commit d92f697, republished under its Apache-2.0 licence (© tetherto). 510 words, ~1,248 tokens.
Download SKILL.mdSave it as
.claude/skills/qv-addon-release-notes/SKILL.md (or your agent's skills folder).- name
- qv-addon-release-notes
- description
- Generate release notes for addon packages (non-SDK inference addons, decoder, OCR). Use when preparing release notes or user asks to "generate release notes" for an addon package.
Addon Release Notes Generator
What
Generate human-readable release notes for addon packages (non-SDK packages like inference addons, decoder, OCR). Collects changes, extracts PRs, validates version bump, and produces a formatted release notes file.
When to Use
- Creating release notes for an addon package
- User explicitly asks to "generate release notes" or "prepare release notes" while working in an addon package
Instructions
Step 1: Identify version and changes (mandatory version bump check)
Identify the full set of changes that will land in main for the PR, and validate the version bump in package.json against main:
Find the PR base and head: The base is
main. The head is the current branch/commit that the PR will merge.Compare against
main:- Use a range like
main...HEAD(or the PR base commit...HEAD) to list commits and diffs. - Always compare
package.jsonbetweenmainandHEAD.
- Use a range like
Mandatory version bump check:
- If the
versioninpackage.jsonis unchanged compared tomain, stop and display this exact warning to the user:
WARNING: VERSION BUMP REQUIRED The
versioninpackage.jsonis unchanged compared tomain. If this PR includes any changes that must be released in the package, you must bump the package version, commit/push it and re-run this command.- If the
Do not include uncommitted changes or untracked files: If any uncommitted/untracked files are present, ignore them.
The goal is to produce a single, combined change set that reflects what will be merged: all commits on the PR branch versus main only.
Step 2: Collect PRs included in this release
- Extract PR numbers from commit messages in the range
main...HEAD- Look for patterns like
#123,(#123), orMerge pull request #123
- Look for patterns like
- For each PR found, use
gh pr view <number>to get:- PR title
- PR number
- PR URL
- Build a list of PRs to include in the release notes
Step 3: Generate Release Notes file
Create release-notes/vX.Y.Z.md with these guidelines:
Show full SKILL.md (204 more words)Show less
Format Requirements
Title:
# QVAC <package_name_readable> v{VERSION} Release NotesReplace<package_name_readable>with a corresponding name:decoder-audio:Audio Decoderembed-llamacpp:Embeddings Addonllm-llamacpp:LLM Addontranslation-nmtcpp:NMT Addontts-onnx:TTS ONNX Addontranscription-whispercpp:Transcription Whisper Addon
Introduction: Write a brief 2-3 sentence summary of what this release brings
Sections: Create each section using narrative prose style. Omit a section if there is no information related with it:
- Breaking Changes: Lead with impact, explain what changed and why, provide clear migration steps with before/after code
- New APIs: Describe what's possible now, show practical usage examples
- Features: Explain benefits in user terms, not just what was added
- Bug Fixes: Describe what was broken and how it's fixed
- Other: Summarize briefly
Pull Requests: At the end, include a "## Pull Requests" section listing all PRs in this release:
markdown ## Pull Requests - [#123](https://github.com/tetherto/qvac/pull/123) - PR title here - [#124](https://github.com/tetherto/qvac/pull/124) - Another PR titleStyle Guidelines:
- Use complete sentences, not bullet fragments
- Lead with benefits/impact
- Group related changes together
- Add context where helpful (why this matters)
- Keep code examples clean and commented
- Remove internal jargon, make it accessible
- Skip entries with no informational value -- generic entries like "Updated models" or "Bumped dependencies" without specific details should be omitted
Example
release-notes/vX.Y.Z.md:
# QVAC OCR Addon v0.4.0 Release Notes
This release introduces automated GitHub releases and improves mobile test reliability.
## Features
### Automated GitHub Releases
The release process is now automated with enforced release notes. When a version bump is detected on merge to main, a GitHub release is automatically created using the corresponding release notes file.
## Bug Fixes
### Mobile E2E Test Workflow Fix
Fixed an issue where mobile E2E tests would fail when the "On PR Trigger" workflow was manually run via workflow_dispatch.
## Pull Requests
- [#67](https://github.com/tetherto/qvac/pull/67) - Fix mobile E2E tests workflow_dispatch
- [#70](https://github.com/tetherto/qvac/pull/70) - feat: automate GitHub releases with mandatory release notes© tetherto, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/qv-addon-release-notes of tetherto/qvac.
Open the folder on GitHubat commit d92f697
Compare with similar skills
Qv Addon Release Notes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Qv Addon Release Notes this skilltetherto/qvac | 674 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Version ReleaseNG-ZORRO/ng-zorro-antd | 9.2k | — | ~3.1k | Automated safety check: Pass | MIT | |
| AionUi Version BumpiOfficeAI/AionUi | 33k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
Version Release
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
AionUi Version Bump
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
Release Round
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
More from tetherto/qvac
All 50 skills in this repoQv Docs Solution Create
tetherto/qvac
Creates a Solutions page in the QVAC documentation website from a real use case, generalizing the case into reusable guidance and registering the page in the site navigation.
Qv Docs Update
tetherto/qvac
Updates the docs website after a change to the SDK or CLI. An agent skill from tetherto/qvac.
Qv Agent Stack Sync
tetherto/qvac
Plan and prepare the QVAC agent-stack release cascade across @qvac/inference, @qvac/sdk, @qvac/cli, @qvac/ai-sdk-provider, @qvac/opencode-plugin, and @qvac/openclaw-plugin.
Qv Quality Reporting
tetherto/qvac
Run the deterministic code-quality audit, turn related findings into contextual remediation groups, prepare approval-gated Asana proposals, reconcile recurring runs, or configure twice-monthly…
Cpp String API Review
tetherto/qvac
Review C++ changes for string parameter and call-site efficiency conventions (std::stringview, std::string&&, const std::string&, const char, and TransparentStringMap lookup).
Qv Addon Changelog
tetherto/qvac
Generate changelog entries for a target add-on package. An agent skill from tetherto/qvac.
Related
Works with
Categories
Questions about Qv Addon Release Notes
What does Qv Addon Release Notes do?
Generate release notes for addon packages (non-SDK inference addons, decoder, OCR). Qv Addon Release Notes is an agent skill from tetherto/qvac. Generate release notes for addon packages (non-SDK inference addons, decoder, OCR).
When should I use Qv Addon Release Notes?
Qv Addon Release Notes fits situations like: preparing release notes; user asks to generate release notes for an addon package.
How do I install Qv Addon Release Notes in Claude Code?
Run `npx skills add tetherto/qvac --skill qv-addon-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/qv-addon-release-notes in tetherto/qvac) into .claude/skills/qv-addon-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Qv Addon Release Notes in Codex?
Run `npx skills add tetherto/qvac --skill qv-addon-release-notes -a codex`. Or copy the skill folder (.agents/skills/qv-addon-release-notes in tetherto/qvac) into .agents/skills/qv-addon-release-notes in your project. Codex loads it when a task matches its description.
Can I use Qv Addon Release Notes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tetherto/qvac --skill qv-addon-release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qv-addon-release-notes, .gemini/skills/qv-addon-release-notes, .github/skills/qv-addon-release-notes and .opencode/skills/qv-addon-release-notes in your project.
What does Qv Addon Release Notes need to run?
Going by SKILL.md and its folder, Qv Addon Release Notes needs the command-line tools its instructions call (gh).
Does Qv Addon Release Notes access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Qv Addon Release Notes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Qv Addon Release Notes use?
Qv Addon Release Notes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Qv Addon Release Notes use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Qv Addon Release Notes?
Skills that share tags, products or a category with Qv Addon Release Notes: Cutting A Release (TriliumNext/Trilium, 38k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars) and Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Qv Addon Release Notes?
tetherto (a GitHub organization) maintains it in tetherto/qvac, which has 674 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.
Source: tetherto/qvac on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.