2K skills · sorted by relevance
Prepare software releases by detecting version files, reviewing changes, and writing changelogs in multiple languages. The workflow updates versions, creates annotated tags with release notes, and can publish GitHub Releases or fill in missing historical releases.
Prepare an Apache bRPC release with tracked progress, version updates, release candidate checks, and draft release notes and emails. The workflow leaves signing, publishing, and other external release actions to the release manager.
Use when preparing for a Salesforce seasonal release — triaging release notes, reviewing Release Updates, opting into Sandbox Preview, and communicating change impact to stakeholders. Triggers: 'upcoming Salesforce release', 'release notes triage', 'Release Updates', 'sandbox preview opt-in', 'release readiness checklist', 'production upgrade date', 'feature impact', 'critical update', 'roll out the Spring release safely', 'is our org ready for the Spring release', 'release update settings metadata', 'FlowSettings release update field', 'release run sheet', 'preview sandbox refresh freeze', 'settings deploy flipped a release update'. Also covers: which Release Updates are deployable as Settings metadata, the release run sheet artefact, and the preview opt-in refresh-date rule. NOT for planning your own release train — use devops/release-management. NOT for user training and go-live comms — use admin/change-management-and-training.
The English summary is being prepared. Showing the original description.
Prepare a software release from the dev branch by turning commits into a changelog, updating the version, and creating a pull request to main. The workflow also covers release tags, branch synchronization, and Homebrew package updates.
Prepare the next Prisma 8 release by updating workspace versions, assembling upgrade guides, and drafting release notes. Open release and documentation pull requests for maintainer review; merging the release request triggers automated publication.
Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.
Check release readiness inside the herdr repository by comparing changes since the base release with upcoming release notes and documentation. Review CLI descriptions, issue references, checks, and benchmarks, then report readiness.
Prepare a stable Paseo release by following the documented release flow and completion checklist. Use it for a fresh patch or minor release, or to promote a beta version to stable.
Polish a published qiankun GitHub Release into readable English and Simplified Chinese notes. The skill clarifies changes, removes repeated entries, preserves package versions and PR references, and updates the release after approval.
Run OpenShell’s Release Canary checks to verify that published development packages and Helm charts install and support basic sandbox operations. Use workflow logs and local Kubernetes reproduction steps to investigate failures before a public release.
Manage OpenSpec releases by auditing merged changes and release records, checking release pull requests, and verifying publication. Support stable and beta releases, resume from the current GitHub state, and finish with polished release notes.
Prepare a Cherry Studio release by checking changes against the published version, writing English and Chinese release notes, updating version metadata, and creating a release branch after review to start the build workflow.
Prepare a beta release of Paseo by following the project's release documentation. The skill directs the agent through the beta workflow and its completion checklist, keeping the task tied to the documented process.
Create the release notes and upgrade guide for a mariadb-operator release. Given the release PR whose body lists every PR included in the release, it gathers each PR, groups the changes by relevance, and produces `docs/releases/RELEASE_<version>_HEADER.md.gotmpl` and `docs/releases/UPGRADE_<version>.md` in the format the previous releases use, then opens a PR targeting `release-<version>`. If no release PR is provided it asks for the new version and infers the changes from git history since the last tag. Use whenever the user wants release notes, an upgrade/update guide, or docs for a new mariadb-operator version — "create the release notes for 26.10.0", "write the upgrade guide", "document this release", "prepare the release PR docs" — even if they don't mention a release PR.
The English summary is being prepared. Showing the original description.
Prepare REA changelogs and GitHub release notes from a fixed Git revision. Turn verified changes into clear user outcomes, preserve accurate contributor credit, and keep the release text aligned with Release Please, the automated release workflow.
Coordinate a complete Paperclip release, from candidate verification and canary testing to stable npm publication and GitHub Release creation. Track release notes, Docker smoke tests, announcement follow-up, and linked content cases when Cases are enabled.
Prepare and guide software releases using rules discovered in the project and its automated build workflows. It tracks version files, helps draft release notes, runs release steps with confirmation, and checks the published result.
Guide a Kortix production release from choosing a version and writing release notes to testing on staging, merging the release pull request, and verifying production. Diagnose blocked promotions and direct fixes back to the dev branch.
Promote the latest qualified OpenShell prerelease to a stable release after maintainer approval. Check that qualification matches the tag and commit, present changes since the previous stable version, and monitor the release workflow through completion.
Prepare an Ant Design Mobile package release by checking the version, build, and package contents. After the user publishes to npm manually, verify the published package and create its Git tag and bilingual GitHub Release.
Prepare and publish a Plannotator release with contributor credits, coordinated version updates, ordered builds, and tag-triggered publishing. The workflow also checks package contents, security scan results, and evidence showing how release files were built.
Build beta versions of the Composio CLI, promote a tested beta to a stable release, and investigate failed releases. Guides verification of published binaries and installation tests through the Build CLI Binaries workflow.
Prepare a Symphony release by updating its version, running checks, merging the change, and tagging the merged commit. Then monitor the Burrito release workflow and verify that the GitHub release contains the expected assets.
Coordinate a game release from candidate preparation through testing, release approval, and deployment. Assign work to role-based agents and collect quality results, patch notes, launch messaging, and a post-release monitoring plan.