sipengxie2024/releasing
skills/releasing/SKILL.md
Use when publishing a new version of the plugin.
$ install --global
skillsauthnpx skillsauth add sipengxie2024/superpower-planning releasingInstall 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: May 7, 2026, 5:24 AM137.3s1 file scanned
SKILL.md
- name:
- releasing
- description:
- Use when publishing a new version of the plugin.
Releasing a New Version
Overview
Bump versions, tag, and publish a GitHub Release with an auto-generated changelog. All version sources must stay in sync.
Version Sources (must match)
| File | Field |
|------|-------|
| .claude-plugin/plugin.json | version |
| .claude-plugin/marketplace.json | plugins[0].version |
| Git tag | vX.Y.Z |
Steps
1. Determine version bump
Check commits since last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Apply semver: patch for fixes, minor for features, major for breaking changes.
2. Generate changelog
Group commits by type when there are enough to justify it:
- Features (
feat:) - Fixes (
fix:) - Refactors (
refactor:) - Other (everything else)
For small releases (< 5 commits), a flat list is fine.
3. Execute release
Once version and changelog are determined, run the release script:
${CLAUDE_PLUGIN_ROOT}/scripts/release.sh "<version>" "<changelog>"
This handles all mechanical steps: update both JSONs → commit → tag → push → create GitHub Release.
Common Mistakes
| Mistake | Fix |
|---------|-----|
| marketplace.json version not updated | Always update both JSON files together |
| Tag created before commit pushed | Push commit first, then tag, or use --tags |
| Changelog missing commits | Use prev_tag..HEAD, not prev_tag..new_tag before tagging |
Related Skills
sipengxie2024/writing-plans
development
VerifiedTrustedCommunity
Use when a spec or requirements exist for a multi-step task and an implementation plan needs to be written before touching code
1SKILL.mdUpdated May 7, 2026
sipengxie2024/verification
data-ai
VerifiedTrustedCommunity
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs.
1SKILL.mdUpdated May 7, 2026
sipengxie2024/team-driven
data-ai
VerifiedTrustedCommunity
Use when executing implementation plans with parallel task groups or individual tasks too heavy for subagent context limits.
1SKILL.mdUpdated May 7, 2026
sipengxie2024/tdd
development
VerifiedTrustedCommunity
Use when implementing any feature or bugfix, before writing implementation code
1SKILL.mdUpdated May 7, 2026