Agent skill

Release

by querylenshq in querylenshq/ef-querylens

A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…

MITAuto-check passedDevelopment

Install Release

skills CLI

$ npx skills add querylenshq/ef-querylens --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install querylenshq/ef-querylens release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/querylenshq/ef-querylens.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "release" agent skill from https://github.com/querylenshq/ef-querylens/tree/main/.github/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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

$skill-installer install https://github.com/querylenshq/ef-querylens/tree/main/.github/skills/release

Type 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.

skills CLI

$ npx skills add querylenshq/ef-querylens --skill release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install querylenshq/ef-querylens release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/querylenshq/ef-querylens.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/release .agents/skills/release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release" agent skill from https://github.com/querylenshq/ef-querylens/tree/main/.github/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.

skills CLI

$ npx skills add querylenshq/ef-querylens --skill release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install querylenshq/ef-querylens release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/querylenshq/ef-querylens.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/release .cursor/skills/release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release" agent skill from https://github.com/querylenshq/ef-querylens/tree/main/.github/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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

$ gemini skills install https://github.com/querylenshq/ef-querylens.git --path .github/skills/release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add querylenshq/ef-querylens --skill release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install querylenshq/ef-querylens release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/querylenshq/ef-querylens.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/release .gemini/skills/release && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "release" agent skill from https://github.com/querylenshq/ef-querylens/tree/main/.github/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.

GitHub CLI

$ gh skill install querylenshq/ef-querylens release

Installs 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).

skills CLI

$ npx skills add querylenshq/ef-querylens --skill release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/querylenshq/ef-querylens.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/release .github/skills/release && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "release" agent skill from https://github.com/querylenshq/ef-querylens/tree/main/.github/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.

skills CLI

$ npx skills add querylenshq/ef-querylens --skill release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install querylenshq/ef-querylens release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/querylenshq/ef-querylens.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/release .opencode/skills/release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release" agent skill from https://github.com/querylenshq/ef-querylens/tree/main/.github/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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: release
GitHub stars: 225
Token cost: ~887 tokens
SKILL.md length: 392 words
Files: 1
Skills in repo: 3
Repo updated: Sep 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…

Works in 9 steps: Verify git working tree is clean → Read the current changelog → Confirm the release version → …
: creating a release
SKILL.md covers Release Workflow and Notes
Calls git

What it does

Release is an agent skill from querylenshq/ef-querylens. Use when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub release, update version, bump version, and update changelog. Covers: changelog extraction/review, semantic version validation, version bumping in VS Code + Rider manifests, guarded git commit/tag flow, and release status messaging.

Its SKILL.md is about 890 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 and Commit messages. It works with Visual Studio Code, Git and GitHub. The repository describes itself as: See the SQL EF Core will generate in real-time while you write LINQ. The licence is MIT.

When your agent uses it

: creating a release
Publishing a version
Cutting a release
Tagging a release

Example prompts

“/release”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

Verify git working tree is clean
Read the current changelog
Confirm the release version
Check the version does not already exist
Update CHANGELOG.md
Bump version references
Commit the version bump
Create and push the tag
Confirm success

What it can do on your machine

Read from SKILL.md and the folder at commit fe73cf3. 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:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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

Release loads about 887 tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 392 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~103
When it runs · the whole SKILL.md, loaded when a task matches: ~887

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 querylenshq/ef-querylens at commit fe73cf3, republished under its MIT licence (© querylenshq). 392 words, ~887 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).

name: release
description: Use when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub release, update version, bump version, and update changelog. Covers: changelog extraction/review, semantic version validation, version bumping in VS Code + Rider manifests, guarded git commit/tag flow, and release status messaging.

Release Skill

Use this skill whenever the user asks to cut a release, tag a version, publish plugins, or create a GitHub release for QueryLens.

Release Workflow

Step 1 — Verify git working tree is clean

Run:

bash

git status --short

If any modified, staged, or untracked files are listed, stop immediately and tell the user:

Working tree is not clean. Please commit or stash all changes before releasing.

Step 2 — Read the current changelog

Read CHANGELOG.md from the repo root. Extract everything under the ## [Unreleased] heading and stop at the next ## [ heading. Display that section to the user so they can review what is going into the release.

If the section is empty, ask:

The [Unreleased] section is empty. Are you sure you want to release with no recorded changes? (yes/no)

If the user answers no, stop.

Step 3 — Confirm the release version

If a version is supplied by the caller, use it. Otherwise ask for one (for example 0.0.3).

Validate that it matches MAJOR.MINOR.PATCH (three numeric segments separated by dots). If invalid, ask again until valid. Store it as VERSION.

Step 4 — Check the version does not already exist

Run:

bash

git tag --list "v$VERSION"

If output is non-empty, stop and tell the user:

Tag v$VERSION already exists. Choose a different version.

Step 5 — Update CHANGELOG.md

Edit CHANGELOG.md at repo root:

Replace the ## [Unreleased] line with:
```
## [Unreleased]

## [VERSION] - YYYY-MM-DD
```
where YYYY-MM-DD is today's ISO date.
Keep the previously unreleased content under the new [VERSION] heading.
Leave the new [Unreleased] section intentionally empty as the next-cycle placeholder.

Show full SKILL.md (144 more words)Show less

Step 6 — Bump version references

Update exactly these files:

src/Plugins/ef-querylens-vscode/package.json set "version" to VERSION
src/Plugins/ef-querylens-rider/gradle.properties set pluginVersion to VERSION

Step 7 — Commit the version bump

Stage exactly these files and commit:

bash

git add CHANGELOG.md \
	src/Plugins/ef-querylens-vscode/package.json \
	src/Plugins/ef-querylens-rider/gradle.properties
git commit -m "chore: release v$VERSION"

Do not add any other files.

Step 8 — Create and push the tag

Run:

bash

git tag v$VERSION
git push origin HEAD
git push origin v$VERSION

The tag push triggers the GitHub Actions release workflow, which:

Builds 6 platform-specific VS Code VSIXes and publishes them to the VS Code Marketplace
Builds the Rider plugin ZIP (with daemon binaries for all 6 RIDs) and publishes it to JetBrains Marketplace
Creates a GitHub Release with all artifacts attached

Step 9 — Confirm success

Tell the user:

✅ Released v$VERSION

Commit pushed to origin

Tag v$VERSION pushed — CI is now building and publishing all three plugins

Check https://github.com/querylenshq/ef-querylens for pipeline status

Notes

This skill is intentionally aligned with .claude/commands/release.md.
If release workflow changes, update both files in the same commit.

Files

Just SKILL.md in .github/skills/release of querylenshq/ef-querylens.

Open the folder on GitHubat commit fe73cf3

Compare with similar skills

Release 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.

Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release this skillquerylenshq/ef-querylens	225	—	~887	Automated safety check: Pass	MIT	1 mo ago
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	2 days ago
Chinese Commit ConventionsjnMetaCode/superpowers-zh	8.3k	1 repos	~1.6k	Automated safety check: Pass	MIT	4 days ago
Codemie Releasecodemie-ai/codemie-code	294	—	~1.8k	Automated safety check: Pass	Apache-2.0	yesterday
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	2 days ago
Draft Release Notesjamiepine/voicebox	57k	—	~941	Automated safety check: Pass	MIT	yesterday

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.
18k GitHub stars~1.9k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Chinese Commit Conventions
jnMetaCode/superpowers-zh
Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.
8.3k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Codemie Release
codemie-ai/codemie-code
Release a new version of CodeMie CLI. An agent skill from codemie-ai/codemie-code.
294 GitHub stars~1.8k tokensUpdated yesterday
DevelopmentAuto-check passed
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
57k GitHub stars~941 tokensUpdated yesterday
DevelopmentAuto-check passed
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
70k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed

Questions about Release

What does Release do?

A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…. Release is an agent skill from querylenshq/ef-querylens. Use when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub release, update version, bump version, and update changelog.

When should I use Release?

Release fits situations like: : creating a release; publishing a version; cutting a release; tagging a release.

How do I install Release in Claude Code?

Run `npx skills add querylenshq/ef-querylens --skill release -a claude-code`. Or copy the skill folder (.github/skills/release in querylenshq/ef-querylens) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.

How do I install Release in Codex?

Run `npx skills add querylenshq/ef-querylens --skill release -a codex`. Or copy the skill folder (.github/skills/release in querylenshq/ef-querylens) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use Release 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 querylenshq/ef-querylens --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release 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 Release use?

Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release use?

About 887 tokens (SKILL.md is roughly 3.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 Release?

Skills that share tags, products or a category with Release: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Chinese Commit Conventions (jnMetaCode/superpowers-zh, 8.3k stars), Codemie Release (codemie-ai/codemie-code, 294 stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

querylenshq (a GitHub organization) maintains it in querylenshq/ef-querylens, which has 225 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 3, 2026.

Source: querylenshq/ef-querylens on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Release Skill

Release Workflow

Step 1 — Verify git working tree is clean

Step 2 — Read the current changelog

Step 3 — Confirm the release version

Step 4 — Check the version does not already exist

Step 5 — Update CHANGELOG.md

Step 6 — Bump version references

Step 7 — Commit the version bump

Step 8 — Create and push the tag

Step 9 — Confirm success

Notes

Files

Compare with similar skills

Similar skills

More from querylenshq/ef-querylens

Related

Questions about Release