mikeparcewski/wicked-garden / .claude/skills/releasing
release
VerifiedRelease management and versioning toolkit for the wicked-garden plugin. Automates changelog generation, semantic versioning, and version bumping from git history. Use when preparing releases, generating changelogs, or managing plugin versions.
Release Tool
Automated release management for the wicked-garden plugin.
Purpose
Streamlines the release process:
- Changelog generation - Auto-generate from commit messages
- Semantic versioning - Intelligent version bumping (major/minor/patch)
- Version management - Update plugin.json, create git tags
- Release notes - Template-based release documentation
Usage
Command Line Mode
# Auto-detect version bump from commits
python3 .claude/skills/releasing/scripts/release.py .
# Specify version bump
python3 .claude/skills/releasing/scripts/release.py . --bump major
python3 .claude/skills/releasing/scripts/release.py . --bump minor
python3 .claude/skills/releasing/scripts/release.py . --bump patch
# Dry run (preview changes)
python3 .claude/skills/releasing/scripts/release.py . --dry-run
# Check if changes exist since last tag
python3 .claude/skills/releasing/scripts/batch_release.py --changed --dry-run
# Force release with bump type
python3 .claude/skills/releasing/scripts/batch_release.py --bump minor
Via Dev Command
/wg-release --dry-run
/wg-release --bump minor
Semantic Versioning Rules
Version Format
MAJOR.MINOR.PATCH (e.g., 1.2.3)
- MAJOR - Breaking changes, incompatible API changes
- MINOR - New features, backwards-compatible functionality
- PATCH - Bug fixes, backwards-compatible fixes
Commit Message Detection
Auto-detect version bump from commit messages:
| Commit Pattern | Version Bump | Example |
|---|---|---|
BREAKING CHANGE:, feat!:, fix!: | major | feat!: redesign cache API |
feat:, feature: | minor | feat: add TTL support |
fix:, bugfix: | patch | fix: handle null keys |
docs:, chore:, refactor: | none | docs: update README |
| No prefix | patch | improve error messages |
Changelog Generation
Commit Categorization
# Changelog
## [1.0.0] - 2026-01-13
### Breaking Changes
- feat!: redesign cache API (#45)
### Features
- feat: add namespace isolation (#42)
- feat: add TTL support with auto-expiration (#43)
### Bug Fixes
- fix: resolve race condition in file writes (#44)
### Documentation
- docs: update README with new API examples
Conventional Commits
Supports Conventional Commits format:
<type>(<scope>): <subject>
[optional body]
[optional footer]
Types: feat, fix, docs, style, refactor, test, chore
Scopes (domain areas): crew, mem, search, jam, engineering, product, platform, qe, data, delivery, agentic, scenarios, patch, observability
Release Workflow
Step-by-Step Process
- Collect commits since last release tag
- Categorize commits by type (breaking, features, fixes)
- Determine version bump from commit types
- Update the version in
.claude-plugin/plugin.json,.claude-plugin/marketplace.jsonand.codex-plugin/plugin.json(node .github/scripts/sync-plugin-version.mjssyncs them to package.json) - Generate CHANGELOG.md entries
- Create git tag (e.g.,
v1.3.0) - Create GitHub release with release notes via
gh release create
Change Detection
The release tool checks for changes in these directories since the last tag:
commands/- Slash commandsagents/- Subagentsskills/- Expertise moduleshooks/- Event bindings and scriptsscripts/- Domain APIsscenarios/- Acceptance tests.claude-plugin/- Plugin metadata
Changes in .claude/ (dev tools) do NOT trigger a release.
Scripts
release.py
Core release engine. Handles version bumping, changelog generation, and git tagging.
batch_release.py
Wrapper that checks for changes since the last tag before releasing.
changelog.py
Generates changelog from git history with commit categorization.
semver.py
Semantic version parsing, comparison, and bumping utilities.
Integration
CI/CD Release Pipeline
# .github/workflows/release.yml
name: Release
on:
push:
branches: [main]
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
fetch-depth: 0 # Full history for changelog
- name: Release if changed
run: python3 .claude/skills/releasing/scripts/batch_release.py --changed
- name: Push tags
run: git push --tags
Best Practices
Commit Messages
- Use conventional commits format
- Include domain scope:
feat(crew): add checkpoint injection - Reference issue numbers (#42)
- Explain "why" not just "what"
Versioning
- Start at 0.1.0 for initial release
- Bump to 1.0.0 when API is stable
- Use pre-release versions for testing (1.0.0-beta.1)
- Never reuse version numbers
Changelog
- Group by category (breaking, features, fixes)
- Include commit hashes for traceability
- Link to issues/PRs where relevant
References
- Semantic Versioning: https://semver.org/
- Conventional Commits: https://www.conventionalcommits.org/
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |