RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
Review and merge the release-plz release PR with explicit user confirmation
Install Source Command Release
$ npx skills add utensils/nxv --skill source-command-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install utensils/nxv source-command-release --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/utensils/nxv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/source-command-release .claude/skills/source-command-release && 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 "source-command-release" agent skill from https://github.com/utensils/nxv/tree/main/.agents/skills/source-command-release into .claude/skills/source-command-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-command-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 install https://github.com/utensils/nxv/tree/main/.agents/skills/source-command-releaseType 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 utensils/nxv --skill source-command-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install utensils/nxv source-command-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/utensils/nxv.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/source-command-release .agents/skills/source-command-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "source-command-release" agent skill from https://github.com/utensils/nxv/tree/main/.agents/skills/source-command-release into .agents/skills/source-command-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-command-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.
$ npx skills add utensils/nxv --skill source-command-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install utensils/nxv source-command-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/utensils/nxv.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/source-command-release .cursor/skills/source-command-release && 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 "source-command-release" agent skill from https://github.com/utensils/nxv/tree/main/.agents/skills/source-command-release into .cursor/skills/source-command-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-command-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 https://github.com/utensils/nxv.git --path .agents/skills/source-command-release--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 utensils/nxv --skill source-command-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install utensils/nxv source-command-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/utensils/nxv.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/source-command-release .gemini/skills/source-command-release && 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 "source-command-release" agent skill from https://github.com/utensils/nxv/tree/main/.agents/skills/source-command-release into .gemini/skills/source-command-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-command-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.
$ gh skill install utensils/nxv source-command-releaseInstalls 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 utensils/nxv --skill source-command-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/utensils/nxv.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/source-command-release .github/skills/source-command-release && 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 "source-command-release" agent skill from https://github.com/utensils/nxv/tree/main/.agents/skills/source-command-release into .github/skills/source-command-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-command-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.
$ npx skills add utensils/nxv --skill source-command-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install utensils/nxv source-command-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/utensils/nxv.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/source-command-release .opencode/skills/source-command-release && 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 "source-command-release" agent skill from https://github.com/utensils/nxv/tree/main/.agents/skills/source-command-release into .opencode/skills/source-command-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-command-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
source-command-release- GitHub stars
- 136
- Token cost
- ~731 tokens
- SKILL.md length
- 372 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review and merge the release-plz release PR with explicit user confirmation
- Works in 5 steps: Locate the release PR → Review what will ship → Pre-flight → …
- Development work in your project
- SKILL.md covers Command Template, Phase 1: Locate the release PR, Phase 2: Review what will ship and Phase 3: Pre-flight, plus 3 more sections
- Calls gh and git
What it does
Source Command Release is an agent skill from utensils/nxv. Review and merge the release-plz release PR with explicit user confirmation
Its SKILL.md is about 730 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. It works with Rust and SQLite. The repository describes itself as: Find any version of any Nix package, instantly. Fast CLI + HTTP API + web UI over 9+ years of indexed nixpkgs history — get the exact commit for nix shell nixpkgs/<commitpkg. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/source-command-release”
Requirements
- Docker
Workflow steps
5 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 82413f0. 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:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and 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
Source Command Release loads about 731 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 372 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 utensils/nxv at commit 82413f0, republished under its MIT licence (© utensils). 372 words, ~731 tokens.
Download SKILL.mdSave it as
.claude/skills/source-command-release/SKILL.md (or your agent's skills folder).- name
- source-command-release
- description
- Review and merge the release-plz release PR with explicit user confirmation
source-command-release
Use this skill when the user asks to run the migrated source command release.
Command Template
Release
Releases are driven by release-plz (release-plz.toml +
.github/workflows/release-plz.yml). On every push to main it maintains a
chore: release vX.Y.Z PR with the version bump and CHANGELOG update derived
from conventional commits. Merging that PR ships the release — release-plz
pushes the vX.Y.Z tag, which triggers release.yml (static binaries, GitHub
release, crates.io, Docker) and flakehub-publish-tagged.yml.
This command walks that flow safely. Never merge the release PR without explicit user confirmation — it is an outward-facing, hard-to-reverse action.
Phase 1: Locate the release PR
gh pr list --repo utensils/nxv --search "chore: release in:title" --state openIf none exists, check whether main has unreleased conventional commits since
the last tag (git log $(git describe --tags --abbrev=0)..origin/main --oneline).
If there are releasable commits but no PR, check the latest Release-plz
workflow run for errors (gh run list --workflow release-plz.yml).
Phase 2: Review what will ship
- Show the PR's version bump (Cargo.toml diff) and CHANGELOG addition.
- Verify the version follows the project convention:
feat:commits bump the 0.x minor (features_always_increment_minor = true), fixes bump patch. - If the version or changelog is wrong, edit the release PR directly (it is a normal editable PR) — release-plz preserves manual edits unless new commits land on main.
Show full SKILL.md (168 more words)Show less
Phase 3: Pre-flight
- All CI checks on the release PR must be green. If checks show "Expected /
Waiting", the App token is misconfigured — see
release-plz.ymlcomments. - Confirm no other PR is about to land that should be in this release.
Phase 4: Confirm and merge
Present a summary (version, commit list, changelog) and require the user to confirm with the explicit version number (AskUserQuestion). Then:
gh pr merge <PR> --repo utensils/nxv --squashPhase 5: Monitor
- The
Release-plzworkflow on main pushes the tag. - The
Releaseworkflow builds binaries and publishes — monitor withgh run list --workflow release.yml/gh run watch. - Verify the GitHub release has all four binaries + SHA256SUMS.txt, crates.io has the new version, and ghcr.io has the version tag.
Manual escape hatches
- Tagging failed after the release PR merged: re-run the
Release-plzworkflow on main (it is idempotent — existing tags are the gate). - The old fully-manual flow (bump Cargo.toml, edit CHANGELOG, tag by hand)
still works in emergencies but must match release-plz's expectations
(tag
vX.Y.Z, CHANGELOG section## [X.Y.Z] - YYYY-MM-DD).
© utensils, 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 .agents/skills/source-command-release of utensils/nxv.
Open the folder on GitHubat commit 82413f0
Compare with similar skills
Source Command 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Source Command Release this skillutensils/nxv | 136 | — | ~731 | Automated safety check: Pass | MIT | |
| RTK Rust Design Patternsrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| BrDicklesworthstone/beads_rust | 1.1k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Projectatlasstyler-ai/ProjectAtlas | 438 | — | ~9.2k | Automated safety check: Pass | MIT | |
| Rust Architectsergigp/yarrtube | 127 | — | ~6.1k | Automated safety check: Pass | MIT | |
| Memorywhale Debuggingwuisabel-gif/MemWhale | 151 | — | ~370 | Automated safety check: Pass | MIT |
Similar skills
Br
Dicklesworthstone/beads_rust
Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.
Projectatlas
styler-ai/ProjectAtlas
Use ProjectAtlas before broad source reads, preferring the installed short atlas CLI for an exact checkout and MCP for registered worktree routing, compact session briefs, or federated graph evidence.
Rust Architect
sergigp/yarrtube
Architecture, naming, and testing conventions guidelines for architecting Rust codebases.
Memorywhale Debugging
wuisabel-gif/MemWhale
MemoryWhale debugging; compiler failures; terminal diagnostics.
Bd To Br Migration
Dicklesworthstone/beads_rust
Migrate docs from bd (beads) to br (beadsrust). An agent skill from Dicklesworthstone/beads_rust.
More from utensils/nxv
Nxv
utensils/nxv
Find any version of any Nix package across nixpkgs git history using the nxv CLI or HTTP API.
Nxv Design
utensils/nxv
A skill your agent uses to generate well-branded interfaces and assets for nxv (Nix Version Index) — either for production or throwaway prototypes/mocks.
Related
Categories
Questions about Source Command Release
What does Source Command Release do?
Review and merge the release-plz release PR with explicit user confirmation. Source Command Release is an agent skill from utensils/nxv.
When should I use Source Command Release?
Source Command Release fits situations like: development work in your project.
How do I install Source Command Release in Claude Code?
Run `npx skills add utensils/nxv --skill source-command-release -a claude-code`. Or copy the skill folder (.agents/skills/source-command-release in utensils/nxv) into .claude/skills/source-command-release in your project. Claude Code loads it when a task matches its description.
How do I install Source Command Release in Codex?
Run `npx skills add utensils/nxv --skill source-command-release -a codex`. Or copy the skill folder (.agents/skills/source-command-release in utensils/nxv) into .agents/skills/source-command-release in your project. Codex loads it when a task matches its description.
Can I use Source Command 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 utensils/nxv --skill source-command-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/source-command-release, .gemini/skills/source-command-release, .github/skills/source-command-release and .opencode/skills/source-command-release in your project.
What does Source Command Release need to run?
Going by SKILL.md and its folder, Source Command Release needs the command-line tools its instructions call (gh and git). Our summary lists: Docker.
Does Source Command Release access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Source Command 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 Source Command Release use?
Source Command 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 Source Command Release use?
About 731 tokens (SKILL.md is roughly 2.9k 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 Source Command Release?
Skills that share tags, products or a category with Source Command Release: RTK Rust Design Patterns (rtk-ai/rtk, 83k stars), Br (Dicklesworthstone/beads_rust, 1.1k stars), Projectatlas (styler-ai/ProjectAtlas, 438 stars) and Rust Architect (sergigp/yarrtube, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Source Command Release?
utensils (a GitHub organization) maintains it in utensils/nxv, which has 136 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 12, 2026.
Source: utensils/nxv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.