prep-release
Skill17 starsChanged 3 days agoApache-2.0View on GitHub
Get fxbot's open release branch ready to cut. Reviews everything since the last tag for gaps, risks, and issues (a report, informational only), brings the docs, guides, changelog, and release notes up to date by Diátaxis, and runs the release-level checks from a clean clone (build, site, migrations from the last release, the image, plugins on the old and new fxbot). Use when the owner runs /prep-release, says a version is nearly done, asks what's left before a release, or wants the branch reviewed, documented, and tested before it ships, even without naming the skill.
- Reads credentials
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- koaning/wigglystufftheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- koaning/wigglystuff★ 455same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- engineeringSkill
- naive-panelSkill
- show-meSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 11
Docs: every change is findable on the right kind of page, and the release notes are drafted.
- Distinctive: line 22
Don't publish: No push, merge, tag, or release.
- Distinctive: line 23
Don't change the machine: No new users, firewall rules, system services, or rootful daemons.
- Distinctive: line 25
Remember this is a public repo: Write no private hostnames, machine names, home paths, personal emails, or secrets.
- Distinctive: line 49
Read references/review.md.
- Distinctive: line 58
Read references/docs.md. It covers Diátaxis, where each kind of change goes in this repo, the house style, and the release notes format.
- Very specific: line 72
Run npm run build-site. It needs Node 22.22 or newer, and it checks links.
- Distinctive: line 74
Look over new files yourself, since that diff doesn't cover them.
- Distinctive: line 81
Read references/checks.md and run every check it lists, from a clean clone of the branch.
- Distinctive: line 100
Ask which version comes next.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prep a release
Get release/<version> ready for the owner to cut, in three passes and a hand-off:
- Review: what this release could break, leave out, or get wrong for owners and plugin authors. Report it, and fix nothing.
- Docs: every change is findable on the right kind of page, and the release notes are drafted.
- Checks: the branch builds, upgrades from the last release, and runs, proven from a clean clone.
The owner cuts the release afterwards, from Cut a release. This skill doesn't bump the version, rename the changelog's section, merge, push, or tag.
Ground rules
Each of these protects something the owner relies on:
- Stay on the release branch in the main tree. The owner's
npm run devruns from it. Vite picks up whatever files are there, so checking out another commit, even for a moment, can leave the owner's app on the wrong code. Put older commits in a clone orgit worktree addunder a temp folder. - Keep every check disposable and your own. Give each one its own database container, data folder, secret key file, and ports. Name containers
fxbot-prep-*. Never point a check at the owner's dev server, its database, or a real install. Run servers from a clone, never from the main tree, whose.envthe server would read. When you finish, stop only what you started, by its saved PID or name, and remove what you made. - Don't publish. No push, merge, tag, or release. A push to
mainpublishes the site, and the release follows. The owner runs those, from commands you give them. - Don't change the machine. No new users, firewall rules, system services, or rootful daemons. If a check needs one, skip it and say so.
- Report only what ran. Each check passed, failed (with its output), or didn't run (with the reason). A lead isn't a finding until you've read the code.
- Remember this is a public repo. Write no private hostnames, machine names, home paths, personal emails, or secrets. Security findings go in the chat report only. The site, README, and notes describe features, not security guarantees.
- Write in plain words. The owner reads everything you write. Use short sentences, say what happens to whom, and define any term you can't avoid.
0. Scope
- The version comes from the argument, or from the branch name
release/<version>. The previous release is the latestv*tag, fromgit describe --tags --abbrev=0 --match 'v*'. Run the scope script from the repository root:
node .agents/skills/prep-release/scripts/scope.mjs [version] [previous tag]. It changes nothing. It prints:- commits and changed areas
- migrations, core and plugins
- each plugin's version,
minFxbot, and changes - plugin API lines removed or changed
- dependency changes and new
FXBOT_variables - docs pages and their sidebar listing
- the phase docs this release touched
- whether the notes file is written
- added lines worth a look: TODOs, home paths, hostnames, secrets
Its
check:lines are leads to look at, not verdicts.- Read
## UnreleasedinCHANGELOG.md, the README's Phases entries marked with this version, andgit log --format='%h %s' <previous>..HEAD. Read each phase doc this release built, indocs/_completed/phases/, closely. Its checklist, open questions, and "What the build changed" say what was promised, what was decided, and what wasn't checked.
Then tell the owner in two or three lines what the release holds, and go on.
1. Review: gaps, risks, and issues
Read references/review.md. It has the lenses, the severity scale, and the report template. Go through each lens against the diff and the phase docs.
- Verify each finding by reading the code it's about. You'll find a lot, and a finding that turns out false costs the owner time and trust.
- For a big release (more than about 60 changed files), split the reading by area across subagents: sdk and server, ui, plugins, then the site and docs. Give each the lenses and ask for
file:lineevidence. Then check what comes back yourself before reporting it. - Report in the chat with the template. Fix nothing in this pass, not even one line. The owner decides what to fix and when, and a quiet fix can't be reviewed.
- Don't wait for an answer. Go on to the docs.
2. Docs
Read references/docs.md. It covers Diátaxis, where each kind of change goes in this repo, the house style, and the release notes format. Then:
- Match the changelog and the commits both ways. A user-visible change with no bullet gets one. A bullet with nothing behind it goes in the report.
- Give each change a home. Find the page that owns it in the map in docs.md, and edit it in place. Write a new page only when nothing owns the change, in exactly one Diátaxis kind, and list it in
packages/website/src/sidebar.ts. - Check the reference pages against the code: the plugin API, HTTP API, client, server API, configuration, and commands. A reference page that's wrong is worse than none.
- Bring the rest up to date with what was built:
- the README's Phases list and Status
AGENTS.md("Where things are" and "What this repo is"), only when the repo's shape changed- each changed plugin's README and description, in
plugin.jsonand inplugins-registry.json - the "What the build changed" notes in each phase doc
- the home page's features, only if a headline feature changed what fxbot is
- Refresh the screenshots. Run
npm run build && npm run shots. It starts a throwaway fxbot with the made-up bots inscripts/screenshots/world.mjs, and rewrites each shot inpackages/website/public/shots/that looks different. Look at every one it rewrote. Don't commit a shot with a broken layout, an error, or anything from a real install. A screen this release added or changed that a guide or the home page should show gets a shot of its own: a scene inshoot.mjs, what the bots say inworld.mjs, and a light and dark<img class="shot">pair in its guide. Commit the shots on their own. - Draft
docs/releases/<version>.mdin the format in docs.md. Leave it uncommitted. It goes in the release commit, which runsgit add docs/releases. - Check the site and whitespace:
- Run
npm run build-site. It needs Node 22.22 or newer, and it checks links. - Run
git diff --check. - Look over new files yourself, since that diff doesn't cover them.
- Run
- Commit the docs on the release branch, by topic. Say in each message what changed, and end it with the session's co-author line.
Fix wrong or missing docs here. A product bug you find while writing them goes in the report, not in a fix.
3. Checks
Read references/checks.md and run every check it lists, from a clean clone of the branch. Keep a row for each one: passed, failed, or not run.
4. Hand-off
End with one short message the owner can act on:
- The verdict: ready, or not ready because of what. Count blockers from the review and failed checks.
- The docs commits, one line each.
- The checks, in a table: check, result, one line of detail.
- What only a person can check, taken from the phase docs: real models, real phones, real accounts.
- The release notes' text, for the owner to read before cutting.
What happens next. When the owner says to cut it, make the release commit locally:
npm version <version> --no-git-tag-version, then rename## Unreleasedto## <version> (<date>), thengit add docs/releases && git commit -am "Release <version>". Run the clean-clone checks again on that commit. Then give the owner this block. It never switches the main tree to another branch:git push origin release/<version> release/<version>:main git fetch origin main:main git switch -c release/<next> && git push -u origin release/<next>Ask which version comes next. The default is the next minor.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

