// Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs `cargo bump` so the generated GitHub notes and the marketing copy land together in `CHANGELOG.md`.
Use this skill when the user asks to "commit all", "commit everything", or wants all outstanding changes committed. Groups unrelated changes into separate, well-described commits instead of one catch-all commit.
Use when creating or substantially editing wiki pages. Covers language, tone, structure, page type selection, linking discipline, and what separates a useful wiki article from filler.
Use when writing or editing any Spacebot copy — README sections, docs, release notes, marketing text, design doc summaries. Covers voice, tone, patterns to avoid, and what good Spacebot writing sounds like.
This skill should be used when the user asks to "review the prompt", "audit the system prompt", "check prompt quality", "inspect what the LLM sees", "debug prompt issues", or "find prompt engineering problems". Pulls the live rendered prompt via the API, explains how it's composed, and reviews it for issues.
This skill should be used when the user asks to change "worker lifecycle", "cancellation", "retrigger behavior", "state machine", "delivery receipts", "timeouts", or "race conditions". Enforces explicit async/state invariants and targeted race-safe verification.
This skill should be used when the user asks to change "Slack adapter", "Telegram adapter", "Discord adapter", "Webhook adapter", "status delivery", "message routing", or "delivery receipts". Enforces cross-adapter parity and explicit delivery semantics.
| name | release-bump-changelog |
| description | Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs `cargo bump` so the generated GitHub notes and the marketing copy land together in `CHANGELOG.md`. |
Create a version bump commit where each release section includes both:
v0.2.0 narrative (clear positioning + concrete highlights).marketing_file="$(mktemp)"$marketing_filecargo bump <patch|minor|major|X.Y.Z> with marketing copy input:
SPACEBOT_RELEASE_MARKETING_COPY_FILE="$marketing_file" cargo bump <...>scripts/release-tag.sh.gh api .../releases/generate-notes).CHANGELOG.md with:
### Release Story (from your marketing file)CHANGELOG.md in the release commit.git show --name-only --statCargo.toml, Cargo.lock (if present), and CHANGELOG.md.git tag --list "v*" --sort=-v:refname | head -n 5).gh CLI installed and authenticated (gh auth status).origin remote points to GitHub, or set SPACEBOT_RELEASE_REPO=<owner/repo>.SPACEBOT_SKIP_MARKETING_COPY=1.Use markdown only (no outer ## vX.Y.Z heading; script adds it). Recommended structure:
Avoid vague hype. Tie claims to concrete shipped changes.
CHANGELOG.md is seeded from historical releases and then maintained by the release bump workflow.