Publish Release

SkillDev tools

Create a GitHub release and publish to NPM.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Publish Release skill

What this skill tells your AI

The instructions your AI receives, as published by itsbencodes/cookies in .claude/skills/publish-release/SKILL.md and read by ahel’s review.

1. Sync main

git fetch origin main --tags
git checkout main
git pull origin main

2. Compute release version

Highest version across publishable packages on origin/main:

VERSION=$(node -p "
  ['react-cookie','universal-cookie','universal-cookie-express','universal-cookie-koa']
    .map(p => JSON.parse(require('child_process').execSync('git show origin/main:packages/'+p+'/package.json')).version)
    .sort((a,b) => a.split('.').map(Number).reduce((_,n,i)=>_||n-b.split('.').map(Number)[i],0))
    .pop()
")
echo "v$VERSION"

Abort if v$VERSION tag already exists:

git rev-parse "v$VERSION" >/dev/null 2>&1 && { echo "Tag v$VERSION already exists"; exit 1; }

3. Tag, push, release

Always create an annotated tag with a message (some local configs enable tag.gpgsign, which makes a plain git tag NAME fail without a message):

git tag -a "v$VERSION" -m "v$VERSION"
git push origin "v$VERSION"
gh release create "v$VERSION" --title "v$VERSION" --generate-notes

Signals

GitHub stars
215
Forks
26
Last commit
May 2026
Advanced
Catalog kind
skill
Gateway key
publish-release
Source
github.com/itsbencodes/cookies