release▌

Centralized release campaign management using RELEASE.md as the single source of truth for all release data, deliverables, and timelines. \n \n Organizes release information across 18 sections covering project snapshot, metadata, narrative, DSP strategy, marketing, PR, physical production, touring, budget, and performance tracking \n Automatically infers artist and release from user context, then creates, reads, or updates the corresponding RELEASE.md document in the releases/{release-slug}/ fol

Write professional press releases with research and fact-checking via inference.sh CLI.

Release planning ensures coordinated deployment of features to production with minimal risk, clear communication, and established rollback procedures.

After shipping, it syncs README, architecture docs, contributing docs, changelog, and related project documentation to match the current code.

Performance benchmarking skill focused on web loads, Core Web Vitals, and regressions across runs or changes.

Post-deploy monitoring loop that watches a live app for page failures, performance regressions, and console issues.

Continues from `/ship` by merging, waiting for CI/deploy completion, and then verifying production health.

Handles release preparation steps such as syncing base, running checks, updating release metadata, pushing, and opening the PR.

This skill provides a systematic workflow for creating and publishing releases for the linear-cli project. It handles changelog management, version bumping, testing, and tagging.

Sanitize code for secrets and artifacts, then create and publish GitHub releases with version tags. \n \n Two-phase workflow: Phase 1 runs blocking checks (secrets scan with gitleaks, LICENSE/README validation, personal artifact removal) and stops on failures; Phase 2 creates version tags and publishes via gh CLI \n Requires gh CLI authenticated, gitleaks installed, and a Git repository with a remote configured \n Includes non-blocking checks for build success and dependency vulnerabilities, plu