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.
Increment the release version, draft release notes, and prepare a GitHub release.
Install Release
$ npx skills add awslabs/loom --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install awslabs/loom 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/awslabs/loom.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/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 "release" agent skill from https://github.com/awslabs/loom/tree/main/.claude/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 install https://github.com/awslabs/loom/tree/main/.claude/skills/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 awslabs/loom --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install awslabs/loom release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/loom.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release .agents/skills/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 "release" agent skill from https://github.com/awslabs/loom/tree/main/.claude/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.
$ npx skills add awslabs/loom --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install awslabs/loom release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/loom.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release .cursor/skills/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 "release" agent skill from https://github.com/awslabs/loom/tree/main/.claude/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 https://github.com/awslabs/loom.git --path .claude/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.
$ npx skills add awslabs/loom --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install awslabs/loom release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/loom.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release .gemini/skills/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 "release" agent skill from https://github.com/awslabs/loom/tree/main/.claude/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.
$ gh skill install awslabs/loom 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 awslabs/loom --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/awslabs/loom.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release .github/skills/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 "release" agent skill from https://github.com/awslabs/loom/tree/main/.claude/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.
$ npx skills add awslabs/loom --skill 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 awslabs/loom release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/loom.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release .opencode/skills/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 "release" agent skill from https://github.com/awslabs/loom/tree/main/.claude/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
- 191
- Token cost
- ~601 tokens
- SKILL.md length
- 297 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Increment the release version, draft release notes, and prepare a GitHub release.
- Works in 6 steps: Read Current Version → Determine New Version → Update Version Files → …
- Tasks that involve Changelog and release notes
- SKILL.md covers Step 1: Read Current Version, Step 2: Determine New Version, Step 3: Update Version Files and Step 4: Commit Version Changes, plus 2 more sections
- Calls git and gh
What it does
Release is an agent skill from awslabs/loom, published by the product's own GitHub organization. Increment the release version, draft release notes, and prepare a GitHub release.
Its SKILL.md is about 600 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 GitHub, Git and npm. The repository describes itself as: Loom for AWS is an enterprise-grade platform for building, deploying, integrating, and operating AI agents on Amazon Bedrock AgentCore. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/release”
Requirements
- Pre-approved tools (allowed-tools): Bash(git *), Bash(gh *), Read, Edit, Grep, Glob
Workflow steps
6 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 4d4dbd6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(git *)Bash(gh *)ReadEditGrepGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and 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
Release loads about 601 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 297 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 awslabs/loom at commit 4d4dbd6, republished under its Apache-2.0 licence (© awslabs). 297 words, ~601 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Increment the release version, draft release notes, and prepare a GitHub release.
- allowed-tools
- Bash(git *), Bash(gh *), Read, Edit, Grep, Glob
- disable-model-invocation
- true
- argument-hint
- [new-version]
Release Preparation
Prepare a new release for the Loom project.
Step 1: Read Current Version
Read the current version from both files:
backend/pyproject.toml— theversionfield under[project]frontend/package.json— the"version"field
Display the current version to the user.
Step 2: Determine New Version
If $ARGUMENTS is provided and is a valid semantic version (e.g. 1.2.0), use it as the new version.
Otherwise, ask the user what the new version should be. Suggest the next patch, minor, and major versions based on the current version (e.g. if current is 1.1.0, suggest 1.1.1, 1.2.0, or 2.0.0).
Wait for the user to confirm before proceeding.
Step 3: Update Version Files
Update the version in all three files:
backend/pyproject.toml: update theversion = "..."linefrontend/package.json: update the"version": "..."linebackend/app/main.py: update bothversion="..."occurrences (FastAPI app and health endpoint)
Step 4: Commit Version Changes
Commit the version bumps:
- Run
git add backend/pyproject.toml frontend/package.json backend/app/main.py - Commit with message
chore: bump version to <new-version>
Step 5: Draft Release Notes
Identify the previous release tag by running git tag --list 'v*' --sort=-version:refname | head -1.
Generate a changelog from commits since that tag: git log <previous-tag>..HEAD --oneline.
Also run git diff <previous-tag>..HEAD --stat to summarize scope.
Draft release notes in markdown with:
- A heading
# v<new-version> Release Notes - Grouped sections by area (features, fixes, infrastructure, docs, etc.)
- A stats line with files changed and lines added/removed
Present the draft to the user for review before proceeding.
Step 6: Prepare GitHub Release
After the user approves the release notes:
- Create a git tag:
git tag v<new-version> - Push the commit and tag:
git push && git push --tags - Create a GitHub release using
gh release create v<new-version> --title "v<new-version>" --notes "<release-notes>"
Confirm each destructive step (push, tag, release creation) with the user before executing.
© awslabs, 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 .claude/skills/release of awslabs/loom.
Open the folder on GitHubat commit 4d4dbd6
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release this skillawslabs/loom | 191 | — | ~601 | Automated safety check: Pass | Apache-2.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 | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Release Clawpatchopenclaw/clawpatch | 813 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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.
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
Release Clawpatch
openclaw/clawpatch
clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.
Release
OvenMediaLabs/OvenPlayer
Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.
More from awslabs/loom
Related
Categories
Questions about Release
What does Release do?
Increment the release version, draft release notes, and prepare a GitHub release. Release is an agent skill from awslabs/loom, published by the product's own GitHub organization. Increment the release version, draft release notes, and prepare a GitHub release.
When should I use Release?
Release fits situations like: tasks that involve Changelog and release notes.
How do I install Release in Claude Code?
Run `npx skills add awslabs/loom --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in awslabs/loom) 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 awslabs/loom --skill release -a codex`. Or copy the skill folder (.claude/skills/release in awslabs/loom) 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 awslabs/loom --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 and gh). Its frontmatter pre-approves these tools: Bash(git *), Bash(gh *), Read, Edit, Grep, Glob.
Does Release access the network?
SKILL.md contains no URLs. Its commands use git and gh, 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 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 Release use?
About 601 tokens (SKILL.md is roughly 2.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: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars) and ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
awslabs (a GitHub organization, an official publisher) maintains it in awslabs/loom, which has 191 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: awslabs/loom on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.