agentleFS
sakurablushsakurablush/zeroagent-studio/.cursor/skills/release-versioning/SKILL.md

release-versioning

Skill4 starsChanged 4 months agoMITView on GitHub

Cut a ZeroAgent Studio release — SemVer bump, CHANGELOG, CI, deploy. Use when shipping user-visible changes.

Files
SKILL.md

Release Versioning

Authority

  • Version: package.json
  • Changelog: CHANGELOG.md (Keep a Changelog)
  • Deploy: push to main → .github/workflows/deploy.yml (GitHub Pages)
  • Fallback: npm run deploy (gh-pages CLI)
  • Live URL: https://sakurablush.github.io/zeroagent-studio/
  • Tool counts in copy: src/lib/siteStats.ts (never hardcode)

Bump decision

LevelWhen
NoneInternal rules/skills only; user deferred release
PatchBug fixes, copy, deps, test-only
MinorNew brain, tool, node type, major Guide feature
MajorBreaking workflow format; removed provider; deploy path change

Workflow

  1. State bump + rationale (one line)
  2. CHANGELOG.md — [Unreleased] or new version section
  3. Bump package.json
  4. npm ci + npm run ci
  5. Push to main when user requests (triggers Pages deploy)

Rule reference

.cursor/rules/release-versioning.mdc

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.