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.
Guide a clean GitWand release end-to-end: bump version, update CHANGELOG, commit, tag, and push.
Install Release
$ npx skills add devlint/GitWand --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install devlint/GitWand 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/devlint/GitWand.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/devlint/GitWand/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/devlint/GitWand/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 devlint/GitWand --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install devlint/GitWand release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devlint/GitWand.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/devlint/GitWand/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 devlint/GitWand --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install devlint/GitWand release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devlint/GitWand.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/devlint/GitWand/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/devlint/GitWand.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 devlint/GitWand --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install devlint/GitWand release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devlint/GitWand.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/devlint/GitWand/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 devlint/GitWand 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 devlint/GitWand --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/devlint/GitWand.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/devlint/GitWand/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 devlint/GitWand --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 devlint/GitWand release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devlint/GitWand.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/devlint/GitWand/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
- 180
- Token cost
- ~1.8k tokens
- SKILL.md length
- 739 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide a clean GitWand release end-to-end: bump version, update CHANGELOG, commit, tag, and push.
- Works in 4 steps: Renommer ## [Unreleased] en ## [X.Y.Z] -… → Ajouter une nouvelle section ##… → Vérifier que toutes les features/fixes… → …
- : make a release
- SKILL.md covers Étape 0 — Identifier le scope, Étape 1 — Vérifications…, Étape 2 — Mettre à jour… and Étape 2b — Mettre à jour…, plus 7 more sections
- Calls git and pnpm; needs APPLE_CERTIFICATE_PASSWORD and APPLE_PASSWORD
What it does
Release is an agent skill from devlint/GitWand. Guide a clean GitWand release end-to-end: bump version, update CHANGELOG, commit, tag, and push. Trigger on: make a release, bump version, publish to npm, ship a new version, create a git tag, update CHANGELOG, release desktop, release CLI, release packages.
Its SKILL.md is about 1.8k 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 and Git workflow. It works with Git, npm, Vue.js and Visual Studio Code. The repository describes itself as: The Git client that actually resolves conflicts: 8 deterministic patterns auto-resolve the ones that were never decisions, full trace on the rest. Native (Tauri 2 + Rust), free… The licence is MIT.
When your agent uses it
- : make a release
- Ship a new version
- Create a git tag
- Update CHANGELOG
Example prompts
- “/release”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Renommer ## [Unreleased] en ## [X.Y.Z] - YYYY-MM-DD
- Ajouter une nouvelle section ## [Unreleased] vide au-dessus
- Vérifier que toutes les features/fixes depuis la dernière release sont documentés
- Ajouter le lien de comparaison en bas du fichier
What it can do on your machine
Read from SKILL.md and the folder at commit 20114ac. 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:
gitpnpm
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 pnpm, 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 these keys or tokens, usually read from environment variables:
APPLE_CERTIFICATE_PASSWORDAPPLE_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release loads about 1.8k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 739 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 devlint/GitWand at commit 20114ac, republished under its MIT licence (© devlint). 739 words, ~1,781 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Guide a clean GitWand release end-to-end: bump version, update CHANGELOG, commit, tag, and push. Trigger on: make a release, bump version, publish to npm, ship a new version, create a git tag, update CHANGELOG, release desktop, release CLI, release packages.
Release — Guide étape par étape
Étape 0 — Identifier le scope
Demander à l'utilisateur quel scope releaser (sauf si le contexte est évident) :
| Scope | Ce qui est publié | Tag git |
|---|---|---|
| monorepo (défaut) | Tout : desktop + npm packages | vX.Y.Z |
| vscode | Extension VS Code uniquement | Versioning indépendant |
Si l'utilisateur dit "je veux bumper la version", "nouvelle release", "publier le CLI", etc. → scope monorepo par défaut.
Étape 1 — Vérifications pré-release
Exécuter dans l'ordre, stopper si l'une échoue :
# 1. Pas de changements non commités
git status
# 2. Sur main (ou branche de release)
git branch --show-current
# 3. À jour avec le remote
git fetch origin && git log origin/main..HEAD --oneline
# 4. Tests passent
pnpm test
# 5. Build réussit
pnpm buildBloquer et signaler si une vérification échoue avant de continuer.
Étape 2 — Mettre à jour CHANGELOG.md (racine)
Ouvrir CHANGELOG.md (racine du repo) et :
- Renommer
## [Unreleased]en## [X.Y.Z] - YYYY-MM-DD - Ajouter une nouvelle section
## [Unreleased]vide au-dessus - Vérifier que toutes les features/fixes depuis la dernière release sont documentés
- Ajouter le lien de comparaison en bas du fichier :
[X.Y.Z]: https://github.com/devlint/GitWand/releases/tag/vX.Y.Z
Format attendu (Keep a Changelog) :
## [Unreleased]
## [2.4.0] - 2026-04-28
### Added
- Support for .prisma resolver
### Fixed
- Context line detection bug in diff parserÉtape 2b — Mettre à jour roadmap.md
Ouvrir roadmap.md et :
- Déplacer les items livrés dans cette release depuis leur section actuelle (In Progress / Planned) vers le bloc Shipped correspondant à la version.
- Si des follow-ups ou limitations ont été identifiés pendant le dev, les ajouter dans la section planifiée appropriée.
Étape 2c — Mettre à jour website/changelog.md
website/changelog.md est le miroir éditorial public — format narratif (prose
et sections thématiques), pas le format Keep a Changelog. Il doit couvrir tout
l'historique depuis v0.0.1.
- Ajouter une nouvelle section
## vX.Y.Z — <Mois> <Année>en tête (après le frontmatter), dans le style éditorial déjà en place. - Rédiger le contenu en prose narrative — titres de features, paragraphes courts. Pas de listes à puces brutes reprises telles quelles du CHANGELOG.
- Vérifier que toutes les versions précédentes sont toujours présentes.
Ne jamais inventer de versions absentes du
CHANGELOG.mdracine.
Étape 2d — Mettre à jour le hero announcement (HomeLanding.vue)
website/.vitepress/theme/HomeLanding.vue contient un pill d'annonce sur la
hero section (.hero-announce, <a class="hero-announce" href="/changelog">)
dont le texte vient de la clé i18n heroAnnounce, dupliquée dans les 5
blocs de locale (fr:, en:, es:, 'pt-BR':, 'zh-CN':).
⚠️
./scripts/bump-version.shNE met PAS à jour ce texte. Le script ne touche ce fichier que pour la constanteLATEST(numéro de version brut) —heroAnnounceest un texte éditorial qui décrit la feature phare de la release, donc il ne peut pas être généré automatiquement. C'est l'oubli le plus fréquent de ce skill : si la hero section du site affiche encore "Nouveau dans la vX.Y" d'une release précédente, c'est que cette étape a été sautée.
- Repérer les 5 occurrences de
heroAnnounce:(une par bloc de locale). - Réécrire chacune pour refléter la feature la plus marquante de cette
release (même angle éditorial que le titre choisi pour
website/changelog.mdà l'étape 2c) — traduire dans les 5 langues, pas juste copier l'anglais. - Format observé :
"Nouveau dans la vX.Y — <feature phare, court>"(fr),"New in vX.Y — <...>"(en), etc. — garder ce gabaritvX.Y(pasvX.Y.Z).
Show full SKILL.md (272 more words)Show less
Étape 3 — Bumper la version
Ne jamais éditer les fichiers de version directement.
Le script met à jour en une seule passe :
apps/desktop/package.jsonapps/desktop/src-tauri/Cargo.tomlapps/desktop/src-tauri/tauri.conf.jsonpackages/core/package.jsonpackages/cli/package.jsonpackages/mcp/package.jsonpackages/mcp/server.json+packages/mcp/src/server.tswebsite/package.json,README.md,website/.vitepress/theme/HomeLanding.vue(uniquement la constanteLATEST— pasheroAnnounce, voir Étape 2d)
# Depuis la racine du repo
./scripts/bump-version.sh X.Y.ZAprès le script, vérifier visuellement :
git diff --statÉtape 4 — Commit + Tag + Push
# Commit le bump de version + CHANGELOG + roadmap + website changelog
git add -A
git commit -m "chore: bump version to X.Y.Z"
# Tag (déclenche release.yml et publish.yml)
git tag vX.Y.Z
# Push avec le tag
git push origin main --tagsÉtape 5 — Surveiller le CI
Rappeler à l'utilisateur de vérifier sur GitHub Actions :
| Workflow | Déclencheur | Durée estimée |
|---|---|---|
release.yml | tag v*.*.* | ~15-20 min (3 plateformes) |
publish.yml | tag v*.*.* | ~2-3 min |
deploy-website.yml | push sur main | ~3-5 min |
Pour le desktop : macOS nécessite un Apple Developer ID configuré (code signing + notarisation). Si le workflow échoue sur la step "sign", vérifier les secrets GitHub (
APPLE_CERTIFICATE,APPLE_CERTIFICATE_PASSWORD,APPLE_SIGNING_IDENTITY,APPLE_ID,APPLE_PASSWORD,APPLE_TEAM_ID).
Cas particulier — Extension VS Code
Le versioning VS Code est indépendant du reste du monorepo (exception à la règle — vsce gère ça) :
# 1. Éditer manuellement la version
# packages/vscode/package.json → "version": "X.Y.Z"
# 2. Packager l'extension
cd packages/vscode && pnpm package
# → génère gitwand-vscode-X.Y.Z.vsix
# 3. Publier
vsce publish
# ou upload manuel sur le VS Code MarketplaceErreurs classiques à éviter
- Bump manuel — toujours passer par
./scripts/bump-version.sh, jamais éditerpackage.json,Cargo.tomloutauri.conf.jsonà la main. - Tag manquant — sans le tag
vX.Y.Z,release.ymletpublish.ymlne se déclenchent pas. - CHANGELOG oublié — mettre à jour avant le commit de bump, pas après.
- roadmap.md oublié — déplacer les shipped items dans le même commit de bump.
- website/changelog.md oublié — doit être mis à jour dans le même commit.
heroAnnounceoublié (HomeLanding.vue) —bump-version.shne le touche pas (voir Étape 2d) ; la hero section du site reste bloquée sur l'annonce de la release précédente si on ne l'édite pas à la main dans les 5 locales.- Push sans
--tags—git push origin mainne pousse pas les tags. Toujoursgit push origin main --tags. - Tests non passés — vérifier
pnpm testavant de bumper, pas après.
© devlint, 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 .claude/skills/release of devlint/GitWand.
Open the folder on GitHubat commit 20114ac
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 skilldevlint/GitWand | 180 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT | |
| AionUi Version BumpiOfficeAI/AionUi | 33k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Git Changes ReporterNo-Trade-No-Life/Yuan | 352 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Markbind Typescript MigrationMarkBind/markbind | 158 | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
AionUi Version Bump
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
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.
Git Changes Reporter
No-Trade-No-Life/Yuan
生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。
Markbind Typescript Migration
MarkBind/markbind
Complete guide for migrating JavaScript files to TypeScript in the MarkBind project, including the two-commit strategy, import/export syntax conversion, and best practices.
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.
More from devlint/GitWand
Add Pattern
devlint/GitWand
Add a new conflict-resolution pattern to GitWand core. An agent skill from devlint/GitWand.
Add Resolver
devlint/GitWand
Add a format-specific resolver to GitWand core. An agent skill from devlint/GitWand.
Add Tauri Command
devlint/GitWand
A skill your agent uses when the user wants to expose a Rust feature to the Vue frontend, add a Tauri IPC command, invoke something from a Vue component, or wire up any backend/frontend…
I18n Sync
devlint/GitWand
Synchronise les fichiers de locale GitWand. An agent skill from devlint/GitWand.
Related
Works with
Categories
Questions about Release
What does Release do?
Guide a clean GitWand release end-to-end: bump version, update CHANGELOG, commit, tag, and push. Release is an agent skill from devlint/GitWand. Guide a clean GitWand release end-to-end: bump version, update CHANGELOG, commit, tag, and push.
When should I use Release?
Release fits situations like: : make a release; ship a new version; create a git tag; update CHANGELOG.
How do I install Release in Claude Code?
Run `npx skills add devlint/GitWand --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in devlint/GitWand) 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 devlint/GitWand --skill release -a codex`. Or copy the skill folder (.claude/skills/release in devlint/GitWand) 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 devlint/GitWand --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 pnpm) and credentials named APPLE_CERTIFICATE_PASSWORD and APPLE_PASSWORD.
Does Release access the network?
SKILL.md contains no URLs. Its commands use git, 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.8k tokens (SKILL.md is roughly 7.1k 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: Hunk Release Workflow (modem-dev/hunk, 9.5k stars), AionUi Version Bump (iOfficeAI/AionUi, 33k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars) and Git Changes Reporter (No-Trade-No-Life/Yuan, 352 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
devlint (a GitHub user) maintains it in devlint/GitWand, which has 180 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.
Source: devlint/GitWand on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.