bjesuiter/jb-release
skills/jb-release/SKILL.md
Use when the user asks to cut, prepare, publish, tag, or verify a release, especially npm/package releases.
testing
Updated Jun 4, 2026
$ install --global
skillsauthnpx skillsauth add bjesuiter/skills jb-releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 4:39 AM156.8s1 file scanned
SKILL.md
- name:
- jb-release
- description:
- Use when the user asks to cut, prepare, publish, tag, or verify a release, especially npm/package releases.
- private:
- true
- allowed-tools:
- Bash(git:*), Bash(gh:*), Bash(npm:*), Bash(pnpm:*), Bash(yarn:*), Bash(bun:*)
- skill_author:
- [email protected]
JB Release
Author: bjesuiter
Purpose
Use this as the generic release skill when preparing a release, cutting a package release, updating a changelog, tagging a version, or publishing artifacts.
Precedence
Repo-specific instructions win. Before acting, check for release guidance in:
AGENTS.md,CLAUDE.md,README.md,CONTRIBUTING.md,CHANGELOG.md- package manager scripts in
package.json - project-specific skills or docs, such as
docs/release*,.github/*, or maintainer notes
If specific instructions exist, follow them instead of this generic workflow. Use this skill only to fill gaps.
Generic release workflow
-
Identify release type and target
- Confirm the package/app to release if the repo has multiple packages.
- Determine version bump:
patch,minor,major, prerelease, or exact version. - If the user did not specify the bump/version, ask before changing files.
-
Inspect current release state
- Check clean/dirty git state with
git status --short. - Find latest tag:
git tag --sort=-version:refname | head. - Review commits since the last release tag:
git log <last-tag>..HEAD --oneline. - Check package metadata and publish scripts.
- Check clean/dirty git state with
-
Update release files
- Update the version in
package.jsonand lockfiles using the repo's package manager when possible. - Add a concise
CHANGELOG.mdentry based on commits since the last release tag. - Keep changelog entries user-facing and grouped when useful: Added, Changed, Fixed, Removed.
- Update the version in
-
Verify
- Run the repo's normal checks before tagging:
- lint
- tests
- build/typecheck
- Prefer existing package scripts over inventing new commands.
- If a check cannot be run, record why.
- Run the repo's normal checks before tagging:
-
Commit, tag, and push
- Commit release changes with a clear message, e.g.
chore: release v1.2.3. - Tag the release commit with the version prefixed by
v, e.g.v1.2.3. - Push code and tags.
- Commit release changes with a clear message, e.g.
-
Publish only when requested or documented
- Do not publish to npm, app stores, or other registries unless the user explicitly asks or repo instructions require it.
- If publishing, use the documented release script/CLI and verify the published version afterward.
Guardrails
- Never create a branch unless the user asks.
- Do not overwrite project-specific release automation.
- Do not skip failing checks silently; stop and report the failure.
- Do not tag before release files are committed and checks have passed, unless repo-specific instructions say otherwise.
- Avoid changing unrelated files during a release.
Deliverable
End with a short summary containing:
- released version
- changelog entry added/updated
- checks run and results
- commit hash and tag
- whether anything was published
Related Skills
bjesuiter/jb-clawpatch-review
testing
VerifiedTrustedCommunity
Use when the user mentions Clawpatch/clawpatch.ai, semantic feature review, repo-wide AI audit, persistent findings, or clawpatch init/map/review/report/fix/revalidate.
SKILL.mdUpdated Jun 4, 2026
bjesuiter/jb-autoreview
development
VerifiedTrustedCommunity
Use when the user asks for autoreview, Codex/Claude second-model review, or final review of dirty changes, a branch, commit, or PR before ship.
SKILL.mdUpdated Jun 4, 2026
bjesuiter/jb-tuna-script
tools
VerifiedTrustedCommunity
Use when adding, writing, fixing, or exposing a script for the Tuna macOS launcher.
SKILL.mdUpdated May 17, 2026
bjesuiter/jb-pinchtab-testing
development
VerifiedTrustedCommunity
Use when smoke-testing a local web app, reproducing frontend bugs, verifying browser flows, or gathering evidence through PinchTab.
SKILL.mdUpdated May 14, 2026