release-manager
starsforks
How to install release-manager?
girijashankarj/cursor-handbook/release-manager
$npx -y skills add girijashankarj/cursor-handbook --skill release-managerManage the full release lifecycle — version bump, changelog, tag, and release notes. Use when the user asks to prepare, create, or publish a release.
SKILL.md
| 1 | # Skill: Release Manager |
| 2 | |
| 3 | Orchestrate the complete release workflow from version bump through tagging and release notes. |
| 4 | |
| 5 | ## Trigger |
| 6 | When the user asks to create a release, bump version, tag a release, or publish release notes. |
| 7 | |
| 8 | ## Prerequisites |
| 9 | - [ ] On `main` or `release/*` branch |
| 10 | - [ ] All CI checks passing |
| 11 | - [ ] No uncommitted changes: `git status --porcelain` |
| 12 | |
| 13 | ## Steps |
| 14 | |
| 15 | ### Step 1: Determine Release Type |
| 16 | - [ ] Analyze commits since last tag: `git log $(git describe --tags --abbrev=0)..HEAD --oneline` |
| 17 | - [ ] Apply semver rules: |
| 18 | |
| 19 | | Commits Include | Bump | Example | |
| 20 | |----------------|------|---------| |
| 21 | | `BREAKING CHANGE` or `!` | **Major** | 1.0.0 → 2.0.0 | |
| 22 | | `feat` | **Minor** | 1.0.0 → 1.1.0 | |
| 23 | | `fix`, `perf`, `refactor` only | **Patch** | 1.0.0 → 1.0.1 | |
| 24 | |
| 25 | - [ ] Confirm with user before proceeding |
| 26 | |
| 27 | ### Step 2: Update Version |
| 28 | - [ ] Update `package.json` version field (if Node.js project) |
| 29 | - [ ] Update any other version references (e.g., `version.ts`, `pyproject.toml`) |
| 30 | - [ ] Update lock file if needed: `npm install --package-lock-only` |
| 31 | |
| 32 | ### Step 3: Generate Changelog |
| 33 | - [ ] Use the `changelog-generator` skill to produce the entry |
| 34 | - [ ] Prepend to `CHANGELOG.md` |
| 35 | - [ ] Review with user |
| 36 | |
| 37 | ### Step 4: Create Release Commit |
| 38 | ```bash |
| 39 | git add package.json package-lock.json CHANGELOG.md |
| 40 | git commit -m "chore(release): vX.Y.Z" |
| 41 | ``` |
| 42 | |
| 43 | ### Step 5: Create Git Tag |
| 44 | ```bash |
| 45 | git tag -a vX.Y.Z -m "Release vX.Y.Z" |
| 46 | ``` |
| 47 | |
| 48 | ### Step 6: Generate Release Notes |
| 49 | Format for GitHub Release: |
| 50 | |
| 51 | ```markdown |
| 52 | ## What's Changed |
| 53 | |
| 54 | ### Highlights |
| 55 | - [Key feature or fix — 1 sentence each] |
| 56 | |
| 57 | ### Added |
| 58 | - feat(scope): description (#PR) |
| 59 | |
| 60 | ### Fixed |
| 61 | - fix(scope): description (#PR) |
| 62 | |
| 63 | ### Breaking Changes |
| 64 | - Description of what broke and migration steps |
| 65 | |
| 66 | **Full Changelog**: https://github.com/org/repo/compare/vPREV...vX.Y.Z |
| 67 | ``` |
| 68 | |
| 69 | ### Step 7: Push & Publish |
| 70 | - [ ] Push commits: `git push origin main` |
| 71 | - [ ] Push tag: `git push origin vX.Y.Z` |
| 72 | - [ ] Create GitHub release: `gh release create vX.Y.Z --title "vX.Y.Z" --notes-file release-notes.md` |
| 73 | - [ ] Verify release appears on GitHub |
| 74 | |
| 75 | ### Step 8: Post-Release |
| 76 | - [ ] Verify CI runs on the tag |
| 77 | - [ ] Verify deployment triggers (if auto-deploy on tag) |
| 78 | - [ ] Notify team (Slack, email, or ticket update) |
| 79 | - [ ] Close related milestone/epic if applicable |
| 80 | |
| 81 | ## Rules |
| 82 | - **ALWAYS** confirm version bump with user before executing |
| 83 | - **ALWAYS** run on clean working tree (no uncommitted changes) |
| 84 | - **NEVER** release from a feature branch |
| 85 | - **NEVER** skip changelog generation |
| 86 | - **NEVER** include secrets or internal URLs in release notes |
| 87 | - Follow semver strictly — breaking changes = major bump |
| 88 | - Tag format: `vX.Y.Z` (with `v` prefix) |
| 89 | |
| 90 | ## Completion |
| 91 | Version bumped, changelog updated, tag created, release notes published. CI/CD triggered for deployment. |
| 92 | |
| 93 | ## If a Step Fails |
| 94 | - **Dirty working tree:** Stash or commit changes first |
| 95 | - **Tag already exists:** Verify version, use next available |
| 96 | - **Push fails:** Check branch protection rules and permissions |
| 97 | - **CI fails on tag:** Fix forward with a patch release, don't delete the tag |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
