xonecas.io
6615
Yc

yoctoselect / files

yoctoselect / .agents / skills / release / SKILL.md

1.5 KB
1---
2name: release
3description: Create a new tagged npm release (patch/minor/major)
4---
5
6Create a new npm release for this repo. The bump type is: $1 (default to "patch" if not provided).
7
8Steps to follow exactly:
9
101. Normalize bump type to one of `patch|minor|major`; if empty, use `patch`.
112. Verify git state before doing anything:
12   - current branch must be `main`
13   - working tree must be clean
14   - run `git fetch origin --tags` and ensure `HEAD` equals `origin/main`
15     If any check fails, stop and report.
163. Run the full repo check suit — stop and report failures.
174. Read `package.json` and capture both `name` and current `version`.
185. Compute the next semver version by bumping the selected part.
196. Guardrails before mutating files:
20   - ensure git tag `v<new-version>` does not exist locally or on origin
21   - ensure npm version does not already exist: `npm view <package-name>@<new-version> version`
22     If either exists, stop and report.
237. Update the `version` field in `package.json` to `<new-version>`.
248. Commit all staged and unstaged changes with message: `chore: release v<new-version>`.
259. Create annotated tag: `git tag -a v<new-version> -m "<small-changelog>"`.
2610. Push explicitly to main and the exact tag:
27    - `git push origin main`
28    - `git push origin v<new-version>`
2911. Post-push verification: run `npm view <package-name>@<new-version> version`.
30    - If it already exists, report that publish already happened and do **not** ask user to publish again.
31    - If it does not exist, run `npm publish`.