npm Release Via GitHub Actions
jmfederico/pi-web
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
Run the claude-code-viewer release flow end-to-end. An agent skill from d-kimuson/claude-code-viewer.
Install Release
$ npx skills add d-kimuson/claude-code-viewer --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install d-kimuson/claude-code-viewer 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/d-kimuson/claude-code-viewer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/d-kimuson/claude-code-viewer/tree/main/.agents/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/d-kimuson/claude-code-viewer/tree/main/.agents/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 d-kimuson/claude-code-viewer --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install d-kimuson/claude-code-viewer release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/d-kimuson/claude-code-viewer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/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/d-kimuson/claude-code-viewer/tree/main/.agents/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 d-kimuson/claude-code-viewer --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install d-kimuson/claude-code-viewer release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/d-kimuson/claude-code-viewer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/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/d-kimuson/claude-code-viewer/tree/main/.agents/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/d-kimuson/claude-code-viewer.git --path .agents/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 d-kimuson/claude-code-viewer --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install d-kimuson/claude-code-viewer release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/d-kimuson/claude-code-viewer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/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/d-kimuson/claude-code-viewer/tree/main/.agents/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 d-kimuson/claude-code-viewer 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 d-kimuson/claude-code-viewer --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/d-kimuson/claude-code-viewer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/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/d-kimuson/claude-code-viewer/tree/main/.agents/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 d-kimuson/claude-code-viewer --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 d-kimuson/claude-code-viewer release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/d-kimuson/claude-code-viewer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/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/d-kimuson/claude-code-viewer/tree/main/.agents/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
- 1.3k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 375 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run the claude-code-viewer release flow end-to-end. An agent skill from d-kimuson/claude-code-viewer.
- Works in 5 steps: Work from the repository root. → Inspect the current branch and working… → If there are unrelated uncommitted… → …
- The user asks to release patch
- SKILL.md covers Inputs, Preconditions, Release command and If push fails because the…, plus 4 more sections
- Calls gh, git and pnpm
What it does
Release is an agent skill from d-kimuson/claude-code-viewer. Run the claude-code-viewer release flow end-to-end. Use when the user asks to release patch, minor, major, beta, or an explicit semver; includes non-interactive release execution, GitHub Actions monitoring with gh, release note cleanup, and publishing the GitHub Release.
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 DevOps & Cloud, covering CI/CD and Changelog and release notes. It works with GitHub and GitHub Actions. The repository describes itself as: A full-featured web-based Claude Code client that provides complete interactive functionality for managing Claude Code projects. The licence is MIT.
When your agent uses it
- The user asks to release patch
- An explicit semver
- Includes non-interactive release execution
- GitHub Actions monitoring with gh
Example prompts
- “/release”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Work from the repository root.
- Inspect the current branch and working tree
- If there are unrelated uncommitted changes, stop and ask the user how to handle them.
- If release-related changes were just made, commit them before running release because scripts/release.ts requires a clean working tree.
- The release script requires SSH signing config
What it can do on your machine
Read from SKILL.md and the folder at commit 9367cf0. 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:
ghgitpnpmnpm
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, pnpm and npm, 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 1.2k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 375 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 d-kimuson/claude-code-viewer at commit 9367cf0, republished under its MIT licence (© d-kimuson). 375 words, ~1,163 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Run the claude-code-viewer release flow end-to-end. Use when the user asks to release patch, minor, major, beta, or an explicit semver; includes non-interactive release execution, GitHub Actions monitoring with gh, release note cleanup, and publishing the GitHub Release.
claude-code-viewer Release
Use this skill to perform an end-to-end release for this repository.
Inputs
Interpret the user's argument as the release version spec:
patch,minor,major,beta- or an explicit semver such as
0.8.0/0.8.0-beta.0
If no version spec is present, ask the user which one to use.
Preconditions
- Work from the repository root.
- Inspect the current branch and working tree:
git branch --show-current
git status --short- If there are unrelated uncommitted changes, stop and ask the user how to handle them.
- If release-related changes were just made, commit them before running release because
scripts/release.tsrequires a clean working tree. - The release script requires SSH signing config:
git config --get gpg.format
git config --get commit.gpgsign
git config --get tag.gpgsignExpected values are ssh, true, true.
Release command
Run the non-interactive release:
VERSION_SPEC="patch" # replace with the user's requested spec
pnpm release -y --version "$VERSION_SPEC"The script runs gatecheck, Lingui validation, tests, and build checks. It then updates package.json, creates a signed release commit, creates a signed tag, and pushes commits and tags.
If push fails because the branch has no upstream
The release commit and tag may already exist locally. Push the current branch with upstream, then push tags:
BRANCH="$(git branch --show-current)"
git push --set-upstream origin "$BRANCH"
git push --tagsDo not rerun pnpm release unless the local release commit/tag were removed or the previous run failed before creating them.
Monitor GitHub Actions
After tags are pushed, find and watch the Release workflow run:
gh run list --workflow Release --limit 5
RUN_ID="<id from the vX.Y.Z row>"
gh run watch "$RUN_ID" --exit-statusA reusable one-liner variant:
TAG="v0.0.0"; RUN_ID="$(gh run list --workflow Release --limit 20 --json databaseId,headBranch,event --jq ".[] | select(.headBranch == \"$TAG\" and .event == \"push\") | .databaseId" | head -n 1)"; test -n "$RUN_ID" && gh run watch "$RUN_ID" --exit-statusIf the workflow fails, inspect logs before taking corrective action:
gh run view "$RUN_ID" --log-failedVerify publish
After the workflow succeeds:
TAG="v0.0.0" # replace
npm view @kimuson/claude-code-viewer version
gh release view "$TAG" --json tagName,name,isDraft,isPrerelease,urlShow full SKILL.md (148 more words)Show less
Fix and publish GitHub Release
The workflow creates a draft release with generated notes. Inspect the generated notes:
TAG="v0.0.0" # replace
gh release view "$TAG" --json body --jq .bodyRewrite the notes for claude-code-viewer users:
- Use concise, user-focused English.
- Prefer these sections when relevant:
Features,Bug Fixes,Breaking Changes,Internal. - Describe the user-visible impact, not implementation details.
- Remove trivial items such as formatting, typo-only, dependency-only, and purely internal refactors unless they affect users.
- Merge intermediate same-release fixes into their related feature or fix.
- Keep each item short and clear.
For a second-pass review before publishing, delegate a focused review to another agent:
RELEASE_URL="https://github.com/d-kimuson/claude-code-viewer/releases/tag/v0.0.0" # replace
pi -p "Review the GitHub Release note at $RELEASE_URL for claude-code-viewer. Check that it is concise, user-focused, correctly categorized, and excludes internal-only noise. Do not edit files or GitHub releases; only report concrete findings."Apply review findings when they are consistent with the rules above. Publish the draft with the rewritten notes:
TAG="v0.0.0" # replace
NOTES_FILE="/tmp/claude-code-viewer-$TAG-release-notes.md"
$EDITOR "$NOTES_FILE" # or write the file with the agent's file tool
gh release edit "$TAG" --notes-file "$NOTES_FILE" --draft=falseConfirm it is public:
gh release view "$TAG" --json tagName,name,isDraft,isPrerelease,urlFinal report
Report:
- released tag/version
- local release command used
- GitHub Actions run ID and result
- npm version verification result
- GitHub Release URL and draft/public state
- any follow-up commits created for release automation or skill updates
© d-kimuson, 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/release of d-kimuson/claude-code-viewer.
Open the folder on GitHubat commit 9367cf0
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 skilld-kimuson/claude-code-viewer | 1.3k | — | ~1.2k | Automated safety check: Pass | MIT | |
| npm Release Via GitHub Actionsjmfederico/pi-web | 866 | — | ~2.9k | Automated safety check: Pass | MIT | |
| OpenWork Release Processdifferent-ai/openwork | 24k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Releasing MarchatCod-e-Codes/marchat | 137 | — | ~801 | Automated safety check: Pass | MIT | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| Kt Search Releasejillesvangurp/kt-search | 155 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
OpenWork Release Process
different-ai/openwork
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
Releasing Marchat
Cod-e-Codes/marchat
Prepares marchat releases: version bumps, CHANGELOG, packaging checksums, GitHub Actions release workflow, and Docker tags.
Cline CLI Release Publisher
cline/cline
Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.
Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
Cicd
RussellSB/pytrendy
A skill your agent uses when touching .github/workflows/, release config (.releaserc), mkdocs.yml, docs deploy, or the whats-new generator.
More from d-kimuson/claude-code-viewer
I18n
d-kimuson/claude-code-viewer
A skill your agent uses when updating Lingui catalogs or fixing translations
Related
Works with
Categories
Questions about Release
What does Release do?
Run the claude-code-viewer release flow end-to-end. An agent skill from d-kimuson/claude-code-viewer. Release is an agent skill from d-kimuson/claude-code-viewer. Run the claude-code-viewer release flow end-to-end.
When should I use Release?
Release fits situations like: the user asks to release patch; an explicit semver; includes non-interactive release execution; GitHub Actions monitoring with gh.
How do I install Release in Claude Code?
Run `npx skills add d-kimuson/claude-code-viewer --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in d-kimuson/claude-code-viewer) 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 d-kimuson/claude-code-viewer --skill release -a codex`. Or copy the skill folder (.agents/skills/release in d-kimuson/claude-code-viewer) 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 d-kimuson/claude-code-viewer --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 (gh, git, pnpm and npm).
Does Release access the network?
SKILL.md contains no URLs. Its commands use gh, git and npm, 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 1.2k tokens (SKILL.md is roughly 4.7k 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: npm Release Via GitHub Actions (jmfederico/pi-web, 866 stars), OpenWork Release Process (different-ai/openwork, 24k stars), Releasing Marchat (Cod-e-Codes/marchat, 137 stars) and Cline CLI Release Publisher (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
d-kimuson (a GitHub user) maintains it in d-kimuson/claude-code-viewer, which has 1,294 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 18, 2026.
Source: d-kimuson/claude-code-viewer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.