| name | release |
| description | Automate a full 5chan release — analyze commits, update release body and blotter, bump version, generate changelog, commit, tag, and push. Use when the user says "release", "new version", "cut a release", "prepare release", or provides a version number to ship. |
Release
End-to-end release automation for 5chan.
Usage
The user provides a version bump (patch, minor, major, or explicit x.y.z).
If omitted, ask which bump level they want.
Workflow
Copy this checklist and track progress:
Release Progress:
- [ ] Step 1: Analyze commits
- [ ] Step 2: Write release body (longer sentence)
- [ ] Step 3: Write blotter message (concise keywords)
- [ ] Step 4: Bump version in package.json
- [ ] Step 5: Generate changelog
- [ ] Step 6: Update blotter file
- [ ] Step 7: Verify blotter
- [ ] Step 8: Commit, tag, push
Step 1 — Analyze commits
git tag --sort=-creatordate | head -1
Then list commits since that tag:
git log --oneline <tag>..HEAD
If there are no new commits, stop — nothing to release.
Categorize by Conventional Commits prefix (feat:, fix:, perf:, refactor:, chore:, etc.).
Step 2 — Write the release body one-liner
Edit oneLinerDescription in scripts/release-body.js (around line 105).
Rules:
- Start with "This version..." or "This release..."
- One sentence, no bullets
