// 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.
| 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. |
End-to-end release automation for 5chan.
The user provides a version bump (patch, minor, major, or explicit x.y.z).
If omitted, ask which bump level they want.
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
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.).
Edit oneLinerDescription in scripts/release-body.js (around line 105).
Rules:
Good examples:
This is a separate, shorter summary used for the in-app blotter banner. The blotter is read by end users — non-developers — so every highlight must be understandable to someone who has never seen the code. This rule is non-negotiable even for internal/infrastructure changes that make it into the blotter.
Format rules:
vX.Y.Z: automaticallyPlain-English rules (apply always, no matter what):
Good examples (the part you write, without the vX.Y.Z: prefix):
Bad examples (and why):
Save this string — you will pass it to the blotter script in Step 6.
Read package.json, compute the new version from the bump level, and update the "version" field.
| Bump | Effect |
|---|---|
patch | 0.6.7 → 0.6.8 |
minor | 0.6.7 → 0.7.0 |
major | 0.6.7 → 1.0.0 |
x.y.z | Set exactly |
yarn changelog
This regenerates CHANGELOG.md from conventional commits.
Pass the blotter message from Step 3 (not the release body):
node scripts/update-blotter.js release --message "<blotter message>"
node scripts/update-blotter.js check
If it fails, fix the issue and re-run.
git add -A
git commit -m "chore(release): v<version>"
git push
git tag v<version>
git push --tags
GitHub Actions triggers on the pushed tag to build release artifacts.
If the user says "dry run" or "preview", execute Steps 1–7 but skip Step 8 (git operations). Print a summary of what would be committed so the user can review.
Resolve on-screen 5chan DOM elements to React source files, line numbers, component names, and ownership stacks using the app's dev-only element-source helpers and playwright-cli. Use when Codex needs to inspect a page element, map a snapshot ref to source code, confirm which component rendered a node, or follow up after $profile-browsing finds a rerender hotspot and needs file-level attribution.
Profile app performance while browsing, collecting Web Vitals and React rerender data via react-scan. Orchestrates parallel profiler subagents via playwright-cli to capture navigation timing, long tasks, layout shifts, LCP, React commit counts, render bursts, and per-component render data. Use when profiling browsing performance, finding bottlenecks, diagnosing excessive rerenders, or auditing page performance.
Profile app performance while browsing, collecting Web Vitals and React rerender data via react-scan. Orchestrates parallel profiler subagents via playwright-cli to capture navigation timing, long tasks, layout shifts, LCP, React commit counts, render bursts, and per-component render data. Use when profiling browsing performance, finding bottlenecks, diagnosing excessive rerenders, or auditing page performance.
Profile app performance while browsing, collecting Web Vitals and React rerender data via react-scan. Orchestrates parallel profiler subagents via playwright-cli to capture navigation timing, long tasks, layout shifts, LCP, React commit counts, render bursts, and per-component render data. Use when profiling browsing performance, finding bottlenecks, diagnosing excessive rerenders, or auditing page performance.
Orchestrates implementation of a multi-task plan by spawning plan-implementer subagents in parallel. Use when the user provides a plan file or plan text and asks to implement it, execute it, or says "implement plan", "run plan", "execute plan".
Test and debug Android APK features using a local Android emulator. Manages emulator lifecycle, builds/installs the APK, runs instrumentation tests, captures logcat diagnostics, and debugs WebView automation (imgur, postimages uploads). Use when the user asks to test APK, debug Android, test uploads, run emulator tests, or says "test-apk".