project-standard-release

Agent Atelier Release

Prepare a release locally (bump version, update CHANGELOG, create the commit and tag), then ask for explicit confirmation before pushing.

This skill writes to the local repo first. It only runs git push after the user explicitly confirms. Without confirmation, the commit + tag stay local.

A release here has no deploy. This repo is a Claude Code plugin marketplace: pushing the tag triggers no workflow — nothing builds, nothing ships to a server. Distribution is the git repo itself (/plugin marketplace add big-emotion/agent-atelier); the GitHub Release is created directly by this skill with gh release create after the push.

When to Activate

• User says: "release project-standard", "cut a release", "bump version", "tag a new version", "ship a release".
• User invokes /project-standard-release (optionally with a bump level: patch | minor | major | <explicit-version>).

Preconditions

Verify all of the following before any write. If any fail, do not modify anything — report the blocker and exit.

1. In the repo root — package.json has "name": "@big-emotion/agent-atelier" (the scoped npm name; the skill prefix stays project-standard). If not, stop and tell the user to cd to the right directory.
2. Clean working tree — git status --porcelain must be empty. If dirty, stop and ask the user to commit or stash.
3. On main branch — git branch --show-current must return main. If not, stop. This is a single-branch repo: main serves as both integration and release branch (deliberate M6 adaptation for a tooling/plugin repo — there is no develop).
4. Up to date with origin/main — run git fetch origin then git rev-list --count main..origin/main. If > 0, stop and tell the user to git pull.
5. CI green on HEAD — run:

   HEAD_SHA=$(git rev-parse HEAD)
   gh run list --repo big-emotion/agent-atelier \
     --commit "$HEAD_SHA" --workflow ci.yml \
     --limit 1 --json conclusion,status,url
   

   The latest run must have conclusion: "success" (ci.yml runs on pushes to main, so HEAD should have a run). If no run exists for HEAD, or the conclusion is not success, stop and provide the run URL so the user can investigate.
6. Local gates green — npm test, npm run check:templates, and npm run check:manifests must all exit 0. This is the repo's whole quality surface (unit tests on the checkers, placeholder-registry validation, marketplace/version lockstep); a release with a red checker would ship broken templates or a drifted marketplace.
7. Manifest versions in sync — every version carrier must already agree before the bump: package.json .version, every plugins/*/.claude-plugin/plugin.json .version, and every .claude-plugin/marketplace.json .plugins[] entry (npm run check:manifests verifies exactly this). If they disagree, stop and report the drift — fix it as a bug first; do not paper over it inside a release.