release
Create a release branch from dev with version bumps and changelog. Use when the user wants to prepare a new release, bump a version, or cut a release. Triggers on phrases like "release 17.1.2", "cut a release", "prepare a release", "version bump", or just "/release".
What this skill does
# Release Create a release branch from `dev` with version bumps and a structured changelog PR. ## Arguments The skill accepts an optional version argument (e.g., `/release 17.1.2`). If no version is provided, read the current version from `package.json` and suggest the next patch version (increment the last number). Confirm with the user before proceeding. ## Instructions ### 1. Pre-flight checks Before anything else, verify the workspace is ready: ```bash git fetch origin git status # must be clean — warn and stop if uncommitted changes git checkout dev git pull ``` Check that `dev` is not behind `main`: ```bash git log dev..origin/main --oneline ``` If `main` has commits not in `dev`, warn the user — they may need to merge main into dev first. ### 2. Determine the version - If a version argument is provided, use it - Otherwise, read `package.json` version, increment the patch number, and confirm with the user ### 3. Create the release branch ```bash git checkout -b release/<version> ``` Branch naming convention: `release/X.Y.Z` (e.g., `release/17.1.2`) ### 4. Update version in these files All files must be updated — the old version appears in each: 1. **`package.json`** — the `"version"` field (line 3) 2. **`server.json`** — TWO version fields, both must match: - Top-level `"version"` (around line 9) - Inside `packages[0].version` (around line 14) 3. **`.claude-plugin/marketplace.json`** (if it exists) — THREE version fields: - `metadata.version` - `plugins[0].version` - `plugins[1].version` (if present) 4. **`package-lock.json`** — run `npm install --package-lock-only` to sync automatically ### 5. Build and verify Run `npm run build` to confirm the project compiles cleanly. If it fails, fix the issue before continuing. ### 6. Commit the version bump Commit message: ``` Bump version to <version> ``` ### 7. Generate the changelog Use `git log` to find all commits on `dev` since the last release merged to main: ```bash git log origin/main..dev --oneline ``` Write a structured changelog summarising the changes. Group related items and focus on what matters to users. Follow this format from previous releases: ``` Release/<version> <Category 1> - Change description - Change description <Category 2> - Change description ``` Example from 17.1.0: ``` Release/17.1.0 SDK Migration - Migrated to @umbraco-cms/mcp-server-sdk npm package - Updated to @modelcontextprotocol/sdk v1.25.1 with new SDK patterns Readonly Mode - Added UMBRACO_READONLY config option to restrict server to read-only operations Tools - Added create-media-folder tool for media library organisation - Improved tool descriptions and property editor templates ``` ### 8. Push and create PR - Push the branch to origin - Create a PR targeting `main` with: - Title: `Release/<version>` - Body: the changelog from step 7 Merging to `main` triggers the npm publish via GitHub Actions. ## Files touched - `package.json` (version field) - `server.json` (2 version fields) - `.claude-plugin/marketplace.json` (3 version fields, if file exists) - `package-lock.json` (auto-updated via npm install)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.