mikeparcewski/release
.claude/skills/releasing/SKILL.md
Release 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.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:58 AM7.5s5 files scanned
SKILL.md
- name:
- release
- description:
- |
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, smaht, mem, search, jam, kanban, 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
.claude-plugin/plugin.jsonversion field - 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
mikeparcewski/skills/engineering/large-scale-migration
development
VerifiedTrustedCommunity
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
8SKILL.mdUpdated Jun 3, 2026
mikeparcewski/wicked-garden:classify
testing
VerifiedTrustedCommunity
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
8SKILL.mdUpdated May 26, 2026
mikeparcewski/wicked-garden:archetype
tools
VerifiedTrustedCommunity
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
8SKILL.mdUpdated May 8, 2026
mikeparcewski/intent
development
VerifiedTrustedCommunity
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
8SKILL.mdUpdated May 6, 2026