| name | release-checklist |
| description | Execute a release in KanbAgent following the full devops + review protocol. Activates when agent devops receives a release ticket, when user says "release", "publish version", "bump version", "npm run release". Covers prerequisites, version bump, CI wait, GitHub Release publication. |
Release Checklist Skill
Step-by-step release process for KanbAgent, extracted from devops and review system prompts.
Who Uses This
- Agent devops — executes the release
- Agent review — creates the release ticket and verifies post-release
Release Ticket Context
Review creates the release ticket with:
- Title: release: bump version X.Y.Z — T
- agent_assigned_id = devops
- agent_validator_id = review
- Listed tickets archived since last release
- Linked to a doc ticket (type bloque)
Version Decision (review's job, before creating ticket)
| Commits since last release | Version bump |
|---|
| fix, chore, refactor only | patch (0.X.Y → 0.X.Y+1) |
| At least one feat | minor (0.X.Y → 0.X+1.0) |
| Breaking change or arch validation | major — requires human confirmation (IvyNotFound) |
Step 1 — Prerequisites (devops checks before anything)
1. Must be on main, clean working tree
git status
git branch --show-current
2. Zero todo/in_progress tickets
node scripts/dbq.js "SELECT COUNT(*) FROM tasks WHERE status IN ('todo', 'in_progress')"
3. Build must pass
npm run build
4. CI E2E tests must pass on HEAD
gh run list --workflow=e2e.yml --branch=main --limit=3 --json headSha,conclusion,status,displayTitle
Verify the run for current HEAD has conclusion=success
(release.sh will check this automatically — step is here for manual verification)
If any prerequisite fails → stop, comment the ticket, set status=blocked.
Never release with open tickets, a broken build, or failing/pending E2E tests on HEAD.
Step 2 — Version Bump
patch (fix, chore only)
npm run release:patch
minor (at least one feat)
npm run release:minor
major (breaking change) — NEVER without explicit human confirmation from IvyNotFound
npm run release:major
This automatically: bumps version in package.json → updates CHANGELOG → commits + tag → pushes.
Step 3 — Wait for CI
gh run watch $(gh run list --workflow=release.yml --limit=1 --json databaseId -q '.[0].databaseId')
Wait for it to complete successfully before going further.
Step 4 — Verify GitHub Release Notes
Check that release notes were auto-injected by CI
gh release view vX.Y.Z
If notes are absent or empty, inject manually:
gh release edit vX.Y.Z --notes-file <(awk "/^## [VERSION]/{f=1;next} f && /^## [/{exit} f{print}" CHANGELOG.md)
Replace VERSION with the actual version number (e.g., 0.25.0).
Step 5 — Publish the Draft
gh release edit vX.Y.Z --draft=false
Step 6 — Close the Ticket
node scripts/dbw.js <<SQL
INSERT INTO task_comments (task_id, agent_id, content)
VALUES (<task_id>, <agent_id>, 'Released vX.Y.Z — CI passed — draft published');
UPDATE tasks SET status='done', completed_at=datetime('now'), updated_at=datetime('now') WHERE id=<task_id>;
SQL
Step 7 — Close the Session
node scripts/dbw.js <<SQL
UPDATE sessions SET tokens_in=X, tokens_out=Y, tokens_cache_read=Z, tokens_cache_write=W,
status='completed', ended_at=datetime('now'),
summary='Done:release vX.Y.Z. CI passed. Draft published.'
WHERE id=<session_id>;
SQL
Hard Rules (from devops system prompt)
- MAJOR bump: explicit confirmation from IvyNotFound mandatory — never decide alone
- Never --no-verify or --no-gpg-sign without explicit lead request
- Never release with todo or in_progress tickets open
- Never release from a branch other than main
- Staged file by file — never git add -A without inspection
- Never release if E2E CI tests are failing or pending on HEAD — release.sh enforces this automatically
Blocked States
If CI fails or prerequisites not met:
UPDATE sessions SET status='blocked', ended_at=datetime('now'),
summary='Blocked:release vX.Y.Z — . Waiting:.' WHERE id=<session_id>;
