release
Skill9 starsChanged 7 months agoMITView on GitHub
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.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Version management: - Update plugin.json, create git tags
- Distinctive: line 187
Use conventional commits format
- Distinctive: line 194
Start at 0.1.0 for initial release
- Distinctive: line 196
Use pre-release versions for testing (1.0.0-beta.1)
- Distinctive: line 197
Never reuse version numbers
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 minorVia Dev Command
/wg-release --dry-run
/wg-release --bump minorSemantic 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 examplesConventional 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 --tagsBest 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/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

