w-release — Claude Code skill: release review and install
w-release is a Claude Code skill that reviews release impact, changelog changes, and template contracts. Invoke it manually; automatic invocation is disabled.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-release -a claude-codeWhat w-release does
w-release compares a feature PR with main or a release PR with the preceding v* tag, then checks changed paths against the repository’s release docs. It suggests a conventional title, flags release classification issues, and reviews effects on the generator CLI, template include/exclude rules, and documentation snapshots.
The skill drafts user-facing changelog bullets and adopter actions, then connects tests with the change classification. For a release PR, it also checks scaffold acceptance. Read the repository’s release docs first. This is advisory only: w-release does not bump versions, merge a release PR, or use publish credentials. It stops if a required human gate is missing.
What it helps with
- assess how a PR affects a release
- suggest a title and flag release classification issues
- draft changelog bullets and adopter actions
- review changes to generator behavior and template rules
Example prompts for the agent
- Review this PR for release impact and suggest a title.
- Compare this release PR with the previous tag and draft changelog bullets.
- Check the template changes and list actions adopters need to take.
How to install w-release
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-release -a claude-code2Manually: put the files in place
~/.claude/skills/w-release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-release/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-release -a codex2Manually: put the files in place
.agents/skills/w-release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-release -a cursor2Manually: put the files in place
.cursor/skills/w-release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-release2Manually: put the files in place
.github/skills/w-release/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-release -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-releaseManually: put the files in place
.devin/skills/w-release/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-release -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about w-release
How do I install w-release in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-release -a claude-code.
What does w-release do?
It reviews PR changes for release impact, changelog updates, classification, and template contract effects. On a release PR, it also checks scaffold acceptance.
Can w-release publish a release or change version numbers?
No. It provides advice only and does not bump versions, merge release PRs, or use publish credentials.
Source text
SKILL.md · MIT
--- name: w-release description: Advisory review of release impact, changelog, and template contracts. disable-model-invocation: true --- Advisory only. Do not bump versions, merge a release PR, or use publish credentials. Read the repository's release docs first. 1. Diff against `main` (feature PR) or the previous `v*` tag (release PR). List payload paths from those docs (Basilic example: `apps/api|web|mobile`, `packages/`, `tools/`, `scripts/`, `.cursor/`, `.agents/`, generator). 2. Suggest a conventional title. Flag `docs`/`chore`/`test`/`ci`/`style` when payload paths changed unless the body has `skip-release: true`. 3. Note generator CLI, template include/exclude, and docs snapshot impact. Generated trees must not gain the documentation app or the generator. 4. Draft user-facing changelog bullets and required adopter actions. Keep the repo's release changelog authoritative (Basilic: Release Please). 5. Link tests, classification, and (on a release PR) scaffold acceptance. Stop if a human gate is missing.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills