alphaclaw: Skill for Claude Code

Release Publish

End-to-end workflow for publishing an AlphaClaw release. Produces release notes in the OpenClaw release format, publishes to npm, creates a GitHub release, closes addressed issues, and drafts a tweet.

Workflow

Phase 1: Gather History

1. Identify the previous stable tag (git tag --sort=-v:refname).
2. Determine the target version. If on a beta prerelease, the stable version is the base (e.g. 0.6.0-beta.3 → 0.6.0). Confirm with the user if unclear.
3. Collect all commits since the last stable tag:

   git log v<prev>..HEAD --oneline --no-merges
   git log v<prev>..HEAD --no-merges --format="----%nCommit: %h%nSubject: %s%n%b"
   

4. Identify external contributors:

   git log v<prev>..HEAD --all --format="%an" | sort | uniq -c | sort -rn
   

5. Find merged PRs and contributor credits:

   git log v<prev>..HEAD --all --merges --format="%s"
   

6. Check open issues on the repo that may be addressed:

   gh issue list --repo chrysb/alphaclaw --state open
   

   Cross-reference issue descriptions against the commit log to identify fixes.

Phase 2: Draft Release Notes

Present a draft to the user before publishing. Use this structure:

## AlphaClaw <version>

### What's New
* **Feature name**: concise description of what it does and why it matters.

### Fixes
* **Short label**: what was broken and how it's fixed. Reference issues
  (`Fixes #N`) and PRs (`(#N)`) inline. Credit external contributors
  (`Thanks @handle.`).

### Contributors
* @handle

Style rules

• Each bullet starts with a bold short label followed by a colon.
• Describe the what and why, not the implementation details.
• Keep What's New and Fixes user-facing: describe behavior, not code structure (no "decomposed into folder-based components", "co-located hooks", etc.). Omit implementation-only changes from the release notes.
• Use active voice ("add", "fix", "remove"), not past tense.
• Reference GitHub issues with Fixes #N (auto-closes) or #N (link only).
• Reference PRs with (#N).
• Credit external contributors with Thanks @handle. at the end of the bullet.
• List all credited contributors in a Contributors section at the bottom.
• Fold reverted commits into their replacement — don't list revert + re-land.