release
Determine the next version, update the marketing site, and run the full release pipeline.
npx skills add Shpigford/chops --skill release --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Cut a new release of Chops. Determines the version from git history, updates the marketing site, and runs the release script. ## Instructions ### Step 1: Verify prerequisites 1. Confirm `.env` exists in the project root. If it does not, stop and tell the user: "Missing `.env` file. Copy `.env.example` to `.env` and fill in APPLE_TEAM_ID, APPLE_ID, and SIGNING_IDENTITY_NAME." 2. Confirm the notarytool keychain profile `AC_PASSWORD` works: ```bash xcrun notarytool history --keychain-profile "AC_PASSWORD" >/dev/null 2>&1 ``` If it fails, stop and tell the user to run: ```bash xcrun notarytool store-credentials "AC_PASSWORD" --apple-id "<APPLE_ID>" --team-id "<TEAM_ID>" --password "<app-specific-password>" ``` 3. Confirm the working tree is clean (`git status --porcelain`). If there are uncommitted changes, stop and tell the user to commit or stash first. 4. Confirm you are on the `main` branch. If not, stop and tell the user to switch to `main` first. ### Step 2: Determine the next version 1. Get the latest tag: ```bash git tag -l 'v*' | sort -V | tail -1 ``` 2. Get commits since that tag: ```bash git log <latest_tag>..HEAD --oneline --format='%s' ``` 3. If there are zero commits sinc
- Instructions
- Step 1: Verify prerequisites
- Step 2: Determine the next version
- Step 3: Confirm the version
- Step 3.5: Update CHANGELOG.md
- Step 4: Update the marketing site version
- Step 5: Run the release script
- Step 6: Push and report
- Important Rules
xcrun notarytool history --keychain-profile "AC_PASSWORD" >/dev/null 2>&1 xcrun notarytool store-credentials "AC_PASSWORD" --apple-id "<APPLE_ID>" --team-id "<TEAM_ID>" --password "<app-specific-password>" git tag -l 'v*' | sort -V | tail -1 git log <latest_tag>..HEAD --oneline --format='%s' git add site/src/pages/index.astro CHANGELOG.md git commit -m "chore: update site version to v<VERSION>" git push
What does the release skill do?
Determine the next version, update the marketing site, and run the full release pipeline.
How do I install it?
Run `npx skills add Shpigford/chops --skill release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Shpigford/chops, a repository with 1,526 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.