release
release
Overview
Workflow to automate the release process for this Claude plugin: select version type, update CHANGELOG, bump version in plugin.json, commit, tag, and push.
Workflow
1. Confirm Version Type
Ask or determine the version bump type based on the changes since the last release:
- patch: Bug fixes, documentation updates, minor improvements (backward-compatible)
- minor: New skills added, new features in backward-compatible manner
- major: Breaking changes (removed/renamed skills, incompatible behavior changes)
2. Check Current Version
jq -r '.version' .claude-plugin/plugin.json
3. Update CHANGELOG.md
Update CHANGELOG.md following the Keep a Changelog format:
- Move the
## [Unreleased]section content to a new versioned section## [X.Y.Z] - YYYY-MM-DD - Add a new empty
## [Unreleased]section at the top
Example:
## [Unreleased]
## [0.8.0] - 2026-03-18
### Added
- Add `agkan-foo` skill for bar workflow
4. Bump Version in plugin.json
Edit .claude-plugin/plugin.json and update the version field manually:
{
"name": "agkan-skills",
"version": "X.Y.Z",
...
}
Verify the version was updated:
jq -r '.version' .claude-plugin/plugin.json
5. Commit Changes
Stage only the relevant files explicitly:
git add .claude-plugin/plugin.json CHANGELOG.md
git commit -m "chore: release vX.Y.Z"
6. Create Git Tag
git tag -a vX.Y.Z -m "Release vX.Y.Z"
Always use the v prefix for git tags (e.g., v0.8.0).
7. Push Commits and Tags
git push origin main --tags
Decision Flow
Determine version type (patch / minor / major)
↓
Update CHANGELOG.md
↓
Bump version in .claude-plugin/plugin.json
↓
git add .claude-plugin/plugin.json CHANGELOG.md
git commit -m "chore: release vX.Y.Z"
↓
git tag -a vX.Y.Z -m "Release vX.Y.Z"
↓
git push origin main --tags
Version Type Selection Guide
| Change Type | Version Bump |
|---|---|
| Bug fixes, typo fixes, documentation updates | patch |
| New skills added, new features (backward-compatible) | minor |
| Removed/renamed skills, breaking behavior changes | major |
Important Notes
- Never skip versions; always increment from the current version
- Always use the
vprefix for git tags (e.g.,v0.8.0) - Always update CHANGELOG.md before creating the release commit
- Do not use
git add -Aorgit add .
More from gendosu/agkan-skills
agkan-planning-subtask
Use when reviewing a single backlog task to assess decomposition, implementation readiness, and priority ordering.
7agkan
Use when managing tasks with the agkan CLI tool - creating, listing, updating tasks, managing tags, blocking relationships, or tracking project progress with the kanban board.
6agkan-review
Use when checking review tasks against GitHub PR status to automatically move them to done or closed.
6agkan-subtask
Use when a task has been selected and you need to implement it in an isolated (forked) context - handles in_progress update, branch creation, implementation, PR creation, and marking review.
6execute-subtask
[DEPRECATED] Use agkan-subtask instead. Use when a task has been selected and you need to implement it in an isolated (forked) context - handles in_progress update, branch creation, implementation, PR creation, and marking done.
6execute-add
[DEPRECATED] Use agkan-add instead. Use when adding a new task to the backlog — collects title, body, tags, priority, and parent task, then creates it with agkan.
6