بنقرة واحدة
swarm-release-kit
يحتوي swarm-release-kit على 12 من skills المجمعة من builtbyberry، مع تغطية مهنية على مستوى المستودع وصفحات skill داخل الموقع.
Skills في هذا المستودع
Recommend the next startable release work from the Swarm Release Manager store — across every release in flight, or within one. Use when the user says /release-next, what is next, what should I work on, or I have a time budget.
Plan a release straight into the shared SRM store: run the structured planning conversation (theme → component sweep → deploy-safety → out-of-scope) and write each confirmed component via component_create — no GitHub issues, no release-plan.json. Use when the user says /srm:release-plan, plan v<X.Y.Z>, plan the next release, scope <release>, or add a component to <release>.
Open a release session against the shared SRM store: confirm the release is seeded, cut the release branch, scaffold the CHANGELOG, open the draft release PR, and optionally (on a yes) link a GitHub milestone. Use when the user says /release-open, start release, cut release branch, or let's start <release>.
Bootstrap a project and release directly in the shared SRM store — born-in-the-store, no GitHub round-trip. Resolve-or-create the workspace project, create the release (theme, version-or-slug, out_of_scope), and offer an optional external-tracker link. Use when the user says /release-init, bootstrap a release in the store, create a project and release in SRM, start a release from scratch, or init a release without a GitHub milestone.
Dispatch parallel work across a release's startable components against the shared SRM store: open a dispatch_run for the wave, then for each member let /srm:release-topic --worktree take the claim and materialize a worktree, and spawn one Claude subagent each that reports progress back to the run. Use when the user says /release-parallel, work on these in parallel, dispatch parallel work, start wave <n>, or run several components concurrently.
Drive the deploy step of a release against the shared SRM store: merge the release PR, watch the deploy, smoke-check production, monitor the window — recording every step on the store's Deploy record so it is resumable across sessions and machines. Use when the user says /release-deploy, deploy the release, ship <release>, or cut over to prod. Deploy-mode only.
Wrap a release against the SRM store: run change-review + readiness (findings land in the store), fill the CHANGELOG, gate on unresolved high findings, and hand off ready-for-deploy. Use when the user says /release-wrap, finish the release, we're ready to close out <release>, or all components are merged, what now. Deploy-mode only.
Run a multi-lens change review over a release component's diff and record the findings in the shared SRM store (not a local review-state file). Loads the configured change lenses, runs them against the component's diff, and writes findings (kind: change) via record_finding; supports defer/accept/fix/re-open via resolve_finding. Use when the user says /srm:change-review, review this component, change review, or attaches a component diff/PR/branch for an SRM-tracked release.
Run a release readiness review and record its findings in the shared SRM store (not a local review-state file). Loads the configured readiness lenses, runs them against the release, and writes findings via record_finding; supports defer/accept/fix/re-open via resolve_finding. Use when the user says /srm:release-readiness, is this release ready, readiness review, pre-release checklist, or asks about migration safety, tenant safety, or deploy readiness for an SRM-tracked release.
Start work on a release component: claim it in the SRM store (the cross-machine lock), then create its topic branch. Use when the user says /release-topic, start <component>, begin work on, or pick up an issue.
Hand a release component's claim back to the SRM store, or force-revoke a stuck one. Use when the user says /release-unclaim, release the claim, drop the hold, or revoke <component>.
Declare a release's dependency graph in the SRM store so components become startable. Use when the user says /release-graph, map dependencies, build the dependency graph, or why is nothing startable.