Agent skill

Release

by rogerpadilla in rogerpadilla/uql

Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site.

MITAuto-check passedDatabases

Install Release

skills CLI
$ npx skills add rogerpadilla/uql --skill release -a claude-code

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

GitHub CLI
$ gh skill install rogerpadilla/uql 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/rogerpadilla/uql.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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/

Facts

Skill name
release
GitHub stars
125
Token cost
~842 tokens
SKILL.md length
427 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site.

  • Works in 6 steps: Review the change → Settle the changelog entry and the level → Commit → …
  • Asked to release
  • SKILL.md covers 1. Review the change, 2. Settle the changelog entry…, 3. Commit and 4. Bump, tag, push, GitHub…, plus 2 more sections
  • Calls bun, gh and lerna

What it does

Release is an agent skill from rogerpadilla/uql. Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site. Use when asked to release, cut a version, publish a package, or ship a patch/minor/major.

Its SKILL.md is about 840 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 Databases, covering Static sites and blogs, Changelog and release notes and ORMs and data access. It works with GitHub, npm, PostgreSQL and SQL. The repository describes itself as: JSON-native TypeScript ORM for Bun, Browsers, Edge, Deno, Node, Workers. The licence is MIT.

When your agent uses it

  • Asked to release
  • Publish a package
  • Ship a patch/minor/major

Example prompts

  • “/release”

Requirements

  • Docker

Workflow steps

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

  1. Review the change
  2. Settle the changelog entry and the level
  3. Commit
  4. Bump, tag, push, GitHub Release
  5. Publish to npm
  6. Update the docs site

What it can do on your machine

Read from SKILL.md and the folder at commit 85f1ac3. 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:

    • bun
    • gh
    • lerna
    • git
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, git and docker, 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 842 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 427 words of instructions outside code blocks.

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

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 rogerpadilla/uql at commit 85f1ac3, republished under its MIT licence (© rogerpadilla). 427 words, ~842 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site. Use when asked to release, cut a version, publish a package, or ship a patch/minor/major.

Releasing uql

"Release" means every step below, not just the bump.

1. Review the change

Everything git status lists, untracked files included, since lerna version leaves them out silently. Understand all of it first, then fix what is wrong, remove/refactor what is unnecesary or over-complicated, unify, simplify, and delete comments the change made stale. Every fix needs a test that failed before it, at the cheapest level that pins it: exact SQL in a dialect spec, cross-backend behaviour in the shared suite. A public API change updates skills/uql-orm/SKILL.md too. Avoid putting unnecesary or overcomplicated code, always unify and simplify for the best clean code (refactor if convenient or necessary to unify or simplify).

bun run check passes, with the databases up (docker compose up -d --wait).

2. Settle the changelog entry and the level

Compress the last entry, unify related bullets together, simplify for humans, only what a user really needs/wants (and what worth it). Rename the heading to the version the bump will produce, dated today. Summarize, simplify and unify.

Nothing checks the level, so take it from the entry. Pre-1.0 a caret range takes every patch of its minor (^0.81.0 is <0.82.0), so a patch reaches users unasked:

  • minor: a **Breaking:** bullet, new API, or a step for the upgrade guide.
  • patch: fixes only.

3. Commit

If the review edited anything important/critical, stop and let the user read that unstaged diff first: everything after the commit is public. Only do a minor release when something important really is released or breaks, otherwise use patch.

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

4. Bump, tag, push, GitHub Release

sh
bun run release patch --yes    # or minor / major: check, bump, commit, tag, push
bun run release.finish         # push again, then the GitHub Release from the changelog entry

Run them apart: release.patch chains the two, but lerna version's prompt hangs a non-interactive shell, and a script's arguments reach only its last command. The codemod gets no GitHub Release, so its bumps notify nobody who never installed it.

From here, never bump again: fix what failed and rerun that step alone (release.finish, release.github, gh run rerun <id>).

5. Publish to npm

The tag push publishes: publish.yml runs once per tag, through npm's trusted publishing. Never publish from a machine, lerna publish included; the packages refuse tokens.

sh
gh run list --workflow publish.yml --limit 2    # one run per package tagged
gh run watch <id> --exit-status

6. Update the docs site

~/projects/uql-site pins uql-orm exactly and compiles every example against it, the skill's included, so it follows a green publish; drafts can start earlier.

  1. bun add --exact uql-orm@<version>.
  2. Document new or changed behaviour; a fix that makes the code match the docs needs nothing. A release that asks anything of users gets a section in upgrade-guide.mdx, a new codemod rewrite a bullet in codemod.md.
  3. bun run check, then commit and push.

© rogerpadilla, MIT. 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 .claude/skills/release of rogerpadilla/uql.

Open the folder on GitHubat commit 85f1ac3

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
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillrogerpadilla/uql125—~842Automated safety check: PassMIT
Frappe Syntax Query BuilderImpertio-Studio/Frappe_Claude_Skill_Package187—~1.7kAutomated safety check: PassMIT
Drizzle Ormericrisco/rsc-harness156—~2.6kAutomated safety check: PassMIT
Tsh SQL And Database UnderstandingTheSoftwareHouse/copilot-collections284—~11kAutomated safety check: PassMIT
Remotion Bits Releaseav/remotion-bits486—~1.2kAutomated safety check: PassNone
Releasehyhmrright/brooks-lint1.5k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Frappe Syntax Query Builder

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when building database queries with frappe.qb in Frappe v14-v16.

    187 GitHub stars~1.7k tokensUpdated 20 days ago
    DatabasesAuto-check passed
  • Drizzle Orm

    ericrisco/rsc-harness

    A skill your agent uses when modeling data or querying with Drizzle ORM in TypeScript — pgTable schema in .ts, type-safe select/insert/relational queries, drizzle-kit migrations.

    156 GitHub stars~2.6k tokensUpdated today
    DatabasesAuto-check passed
  • Tsh SQL And Database Understanding

    TheSoftwareHouse/copilot-collections

    SQL writing and database engineering patterns, standards, and procedures.

    284 GitHub stars~11k tokensUpdated 2 days ago
    DatabasesAuto-check passed
  • Remotion Bits Release

    av/remotion-bits

    Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.

    486 GitHub stars~1.2k tokensUpdated 21 days ago
    DevelopmentAuto-check passed
  • Release

    hyhmrright/brooks-lint

    Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG…

    1.5k GitHub stars~1.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Release New Version

    kcsujeet/ilamy-calendar

    Cut a new release of @ilamy/calendar — analyze commits since the last tag, suggest a semver bump, draft a CHANGELOG entry in the project's existing style, run the CI gate, commit, tag, push to…

    351 GitHub stars~5.8k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from rogerpadilla/uql

  • Uql Orm

    rogerpadilla/uql

    Write code with UQL (the uql-orm package), the TypeScript ORM whose queries are plain JSON objects, on PostgreSQL, MySQL, MariaDB, SQLite, CockroachDB, SQL Server, MongoDB, Turso, Neon, D1 and PGlite.

    125 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

Questions about Release

What does Release do?

Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site. Release is an agent skill from rogerpadilla/uql. Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site.

When should I use Release?

Release fits situations like: asked to release; publish a package; ship a patch/minor/major.

How do I install Release in Claude Code?

Run `npx skills add rogerpadilla/uql --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in rogerpadilla/uql) 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 rogerpadilla/uql --skill release -a codex`. Or copy the skill folder (.claude/skills/release in rogerpadilla/uql) 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 rogerpadilla/uql --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 (bun, gh, lerna, git and docker). Our summary lists: Docker.

Does Release access the network?

SKILL.md contains no URLs. Its commands use gh, git and docker, 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 842 tokens (SKILL.md is roughly 3.4k 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: Frappe Syntax Query Builder (Impertio-Studio/Frappe_Claude_Skill_Package, 187 stars), Drizzle Orm (ericrisco/rsc-harness, 156 stars), Tsh SQL And Database Understanding (TheSoftwareHouse/copilot-collections, 284 stars) and Remotion Bits Release (av/remotion-bits, 486 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

rogerpadilla (a GitHub user) maintains it in rogerpadilla/uql, which has 125 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.

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