[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EE4K2XER42Q99VB330NB3V":3,"skill-same:01M7EE4K2XER42Q99VB330NB3V":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EE4K2XER42Q99VB330NB3V","release",null,"antoine-tena\u002Fion-repo","antoine-tena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F246046300?v=4","01M7EE1A7TQJKDACMM6WV5VEVY","Antoine-Tena","01M7EE1A8C65TRR9E6FKXEXBG3",3,"MIT","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release\ndescription: Ships a release: release\u002FvX.Y.Z branch, full checks, announcement, main tagged, deployment, back into develop. Use to release, ship, deploy a version, or for an urgent production fix.\nargument-hint: \"[vX.Y.Z] [develop commit]\"\n---\n\nOnly a release reaches production: `develop` integrates without full CI (`\u002Frepo:merge`), the release runs every check. Git Flow: `release\u002FvX.Y.Z` from `develop` takes only fixes, merges into `main` (tag `vX.Y.Z`) and back into `develop`. Urgent production fix: same path from `main`'s latest tag, on `hotfix\u002FvX.Y.Z`.\n\nRead first the project's `CLAUDE.md` (`[RELEASES]` or \"Releases\"): announcement (what's-new, email), deployment commands, extra checks. Stop if no production `main`. Talk in the user's language. Never switch the main tree's branch: each in `.claude\u002Fworktrees\u002F\u003Cname>` (`release-vX.Y.Z`, `main`).\n\n## ion-repo's own repo\nNo production: the tag publishes. These replace the steps below.\n1. `ion repo version`: candidates, proposed number, plan tickets still open.\n2. `ion repo version cut` (`--minor` for a milestone decided by its owner): branch `release\u002FvX.Y.Z` in `.claude\u002Fworktrees\u002Frelease-vX.Y.Z`, `CHANGELOG.md` drafted, numbers bumped. Rewrite the entry for users (breaking first, each with its conversion by `ion repo update`; keep `- **After updating**: …` lines, which become backlog tickets), delete the draft line, commit; `ion repo version cut` again: full checks, tag `-rc.N` pushed. Candidate fix: `fix:` commit, `cut` again.\n3. `ion repo version promote` when `ion repo version` says ready (`--urgent` only if its owner asks: no soak nor repo, green CI still required): tag on its exact commit, merged into `main` and `develop`; `pypi.yml` publishes package and GitHub Release.\n4. `ion repo update --all` only with the user's yes.\n\n## 1. Choose\n- `git fetch origin --tags`. Previous: `git describe --tags --abbrev=0 origin\u002Fmain`.\n- Candidate: argument, else `origin\u002Fdevelop`. Urgent fix: latest tag plus only the fix's commits (`git cherry-pick`).\n- Number: argument, else project's `CLAUDE.md` (ion-repo: next patch, breaking included, minor only for an owner-decided milestone; `ion repo version` proposes), else semver as `vX.Y.Z`, never `v2`: next minor with `feat`, next patch with only fixes, next major only for a breaking change after 1.0; the first release is `v0.1.0`.\n- Changes: `git log --first-parent --format='%h %s' \u003Cprevious>..\u003Ccandidate>`. Work left out: take an older candidate, don't undo code on the release.\n- `\u002Frepo:review --repo`. The release note says clearly what a poor subject hides.\n\n## 2. Cut\n`git worktree add .claude\u002Fworktrees\u002Frelease-vX.Y.Z -b release\u002FvX.Y.Z \u003Ccandidate>`, `git push -u origin release\u002FvX.Y.Z`. Then only `fix:` commits, never a feature.\n\n## 3. Risks since previous release\n- **Migrations** (`*\u002Fmigrations\u002F`): schema, data, reversible? Deployment applies after backup; flag irreversible.\n- **Settings**: new env variables (`config(`, `runtimeConfig`, `.env.example`); check they exist in production before deploying.\n- **API contract**: routes or fields removed or renamed in `openapi.json`; a cached front calls the old one. Deploy API, then front.\n- **Flags**: features shipped off, planned production state.\n- **Dependencies** added or major-bumped.\n\n## 4. Announcement\nPer `CLAUDE.md`, which keeps where it goes and how it is sent. Check it exists for `vX.Y.Z`, describes the risks found, promises neither work left out nor a feature behind a flag staying off. Otherwise write it on the release: through `\u002Fwords:announce vX.Y.Z` when the `words` plugin is installed (`claude plugin list`), else by hand; either way **have the user approve the text**.\n\n## 5. Full checks\n`ion repo ci release\u002FvX.Y.Z` (or GitHub CI on the branch): every job. Failure: fix on the release, commit, rerun until green. Report jobs not replayed.\n\n## 6. Go-ahead\nShow briefly: number, changes, risks, announcement, CI verdict, rollback (previous release). Wait for agreement: this is production.\n\n## 7. Merge and tag\n```bash\ngit worktree add .claude\u002Fworktrees\u002Fmain main\ngit -C .claude\u002Fworktrees\u002Fmain merge --no-ff release\u002FvX.Y.Z -m \"Release vX.Y.Z: \u003Csummary>\"\ngit -C .claude\u002Fworktrees\u002Fmain tag -a vX.Y.Z -m \"Release vX.Y.Z\" -m \"\u003Cchanges, one line each>\"\ngit push origin main vX.Y.Z && git worktree remove .claude\u002Fworktrees\u002Fmain\n```\n`main`'s commit holds the release's files: the deploy script accepts its `ion repo ci` verdict (`green-ci.sh`), no CI replay.\n\n## 8. Deploy\nProject's commands (often `scripts\u002Fops\u002Fdeploy-backend.sh --dry-run`, then without, then `deploy-frontend.sh`; dashboard alone: `deploy-frontend.sh` only), API before front. Then check: script's smoke test, production logs a few minutes (project's diagnosis skill if any), announcement visible. Breakage: back to the previous release via the project's procedure, and say so.\nNo deployment (no `scripts\u002Fops\u002Fdeploy-*.sh`, nothing in `CLAUDE.md`): release ends at the tag on `main`; say so, go to step 9.\nPyPI command (`.github\u002Fworkflows\u002Fpypi.yml`, `ion repo set pypi_name=…`): pushed tag deploys, version `X.Y.Z` from `vX.Y.Z`. `gh run watch`, then check `https:\u002F\u002Fpypi.org\u002Fproject\u002F\u003Cpypi_name>\u002FX.Y.Z\u002F`; a red run names its step. First tag needs either a `PYPI_TOKEN` secret in the `pypi` environment (\"Entire account\" to create the project, `\u002Frepo:token`), or a publisher on https:\u002F\u002Fpypi.org\u002Fmanage\u002Faccount\u002Fpublishing\u002F (repository, workflow `pypi.yml`, environment `pypi`). A PyPI version can never be re-uploaded: fix a broken one with the next tag.\n\nActions blocked (billing): don't wait on a queued run, whose job can sit for minutes before the refusal shows in its annotations; `gh run cancel` it, so it cannot publish later, and publish from the machine. The repo stays untouched:\n```bash\ndir=\"$(mktemp -d ~\u002F.cache\u002Fpublish.XXXXXX)\"\ngit archive vX.Y.Z | tar -x -C \"$dir\"\ncd \"$dir\"                                              # then the backend directory, if any\nuv version --frozen X.Y.Z\nuv build --out-dir dist\nuvx --isolated --from dist\u002F*.whl \u003Ccommand> --version   # and --help of each area\nUV_PUBLISH_TOKEN=\"$(cat \u003Crepo root>\u002F.pypi\u002Ftoken)\" uv publish dist\u002F*\n```\nThen check the project's page as above and delete `$dir`. Token: only the repo's own `.pypi\u002F`, never printed. None: stop, `\u002Frepo:token`; another repo's only with the user's yes. Say in the report that this upload has no build provenance (`attest-build-provenance` runs only on GitHub). `pypi.yml` stays: budget back, the next tag publishes with provenance; meanwhile a failed run per tag is the only cost.\n\n## 9. Merge back, tidy\n```bash\ngit merge --no-ff release\u002FvX.Y.Z -m \"Merge branch 'release\u002FvX.Y.Z' into develop\"   # from develop\ngit push origin develop\ngit worktree remove .claude\u002Fworktrees\u002Frelease-vX.Y.Z\ngit branch -d release\u002FvX.Y.Z && git push origin --delete release\u002FvX.Y.Z\n```\nReport in the `repo` plugin's `debrief` format (`output-styles\u002Fdebrief.md`); a failed health probe or smoke test is a `Broken:` line.\n","Only a release reaches production: `develop` integrates without full CI (`\u002Frepo:merge`), the release runs every check. Git Flow: `release\u002FvX.Y.Z` from `develop` takes only fixes, merges into `main` (tag `vX.Y.Z`) and back into `develop`. Urgent production fix: same path from `main`'s latest tag, on `hotfix\u002FvX.Y.Z`.\n\nRead first the project's `CLAUDE.md` (`[RELEASES]` or \"Releases\"): announcement (what's-new, email), deployment commands, extra checks. Stop if no production `main`. Talk in the user's language. Never switch the main tree's branch: each in `.claude\u002Fworktrees\u002F\u003Cname>` (`release-vX.Y.Z`, `main`).\n\n## ion-repo's own repo\nNo production: the tag publishes. These replace the steps below.\n1. `ion repo version`: candidates, proposed number, plan tickets still open.\n2. `ion repo version cut` (`--minor` for a milestone decided by its owner): branch `release\u002FvX.Y.Z` in `.claude\u002Fworktrees\u002Frelease-vX.Y.Z`, `CHANGELOG.md` drafted, numbers bumped. Rewrite the entry for users (breaking first, each with its conversion by `ion repo update`; keep `- **After updating**: …` lines, which become backlog tickets), delete the draft line, commit; `ion repo version cut` again: full checks, tag `-rc.N` pushed. Candidate fix: `fix:` commit, `cut` again.\n3. `ion repo version promote` when `ion repo version` says ready (`--urgent` only if its owner asks: no soak nor repo, green CI still required): tag on its exact commit, merged into `main` and `develop`; `pypi.yml` publishes package and GitHub Release.\n4. `ion repo update --all` only with the user's yes.\n\n## 1. Choose\n- `git fetch origin --tags`. Previous: `git describe --tags --abbrev=0 origin\u002Fmain`.\n- Candidate: argument, else `origin\u002Fdevelop`. Urgent fix: latest tag plus only the fix's commits (`git cherry-pick`).\n- Number: argument, else project's `CLAUDE.md` (ion-repo: next patch, breaking included, minor only for an owner-decided milestone; `ion repo version` proposes), else semver as `vX.Y.Z`, never `v2`: next minor with `feat`, next patch with only fixes, next major only for a breaking change after 1.0; the first release is `v0.1.0`.\n- Changes: `git log --first-parent --format='%h %s' \u003Cprevious>..\u003Ccandidate>`. Work left out: take an older candidate, don't undo code on the release.\n- `\u002Frepo:review --repo`. The release note says clearly what a poor subject hides.\n\n## 2. Cut\n`git worktree add .claude\u002Fworktrees\u002Frelease-vX.Y.Z -b release\u002FvX.Y.Z \u003Ccandidate>`, `git push -u origin release\u002FvX.Y.Z`. Then only `fix:` commits, never a feature.\n\n## 3. Risks since previous release\n- **Migrations** (`*\u002Fmigrations\u002F`): schema, data, reversible? Deployment applies after backup; flag irreversible.\n- **Settings**: new env variables (`config(`, `runtimeConfig`, `.env.example`); check they exist in production before deploying.\n- **API contract**: routes or fields removed or renamed in `openapi.json`; a cached front calls the old one. Deploy API, then front.\n- **Flags**: features shipped off, planned production state.\n- **Dependencies** added or major-bumped.\n\n## 4. Announcement\nPer `CLAUDE.md`, which keeps where it goes and how it is sent. Check it exists for `vX.Y.Z`, describes the risks found, promises neither work left out nor a feature behind a flag staying off. Otherwise write it on the release: through `\u002Fwords:announce vX.Y.Z` when the `words` plugin is installed (`claude plugin list`), else by hand; either way **have the user approve the text**.\n\n## 5. Full checks\n`ion repo ci release\u002FvX.Y.Z` (or GitHub CI on the branch): every job. Failure: fix on the release, commit, rerun until green. Report jobs not replayed.\n\n## 6. Go-ahead\nShow briefly: number, changes, risks, announcement, CI verdict, rollback (previous release). Wait for agreement: this is production.\n\n## 7. Merge and tag\n```bash\ngit worktree add .claude\u002Fworktrees\u002Fmain main\ngit -C .claude\u002Fworktrees\u002Fmain merge --no-ff release\u002FvX.Y.Z -m \"Release vX.Y.Z: \u003Csummary>\"\ngit -C .claude\u002Fworktrees\u002Fmain tag -a vX.Y.Z -m \"Release vX.Y.Z\" -m \"\u003Cchanges, one line each>\"\ngit push origin main vX.Y.Z && git worktree remove .claude\u002Fworktrees\u002Fmain\n```\n`main`'s commit holds the release's files: the deploy script accepts its `ion repo ci` verdict (`green-ci.sh`), no CI replay.\n\n## 8. Deploy\nProject's commands (often `scripts\u002Fops\u002Fdeploy-backend.sh --dry-run`, then without, then `deploy-frontend.sh`; dashboard alone: `deploy-frontend.sh` only), API before front. Then check: script's smoke test, production logs a few minutes (project's diagnosis skill if any), announcement visible. Breakage: back to the previous release via the project's procedure, and say so.\nNo deployment (no `scripts\u002Fops\u002Fdeploy-*.sh`, nothing in `CLAUDE.md`): release ends at the tag on `main`; say so, go to step 9.\nPyPI command (`.github\u002Fworkflows\u002Fpypi.yml`, `ion repo set pypi_name=…`): pushed tag deploys, version `X.Y.Z` from `vX.Y.Z`. `gh run watch`, then check `https:\u002F\u002Fpypi.org\u002Fproject\u002F\u003Cpypi_name>\u002FX.Y.Z\u002F`; a red run names its step. First tag needs either a `PYPI_TOKEN` secret in the `pypi` environment (\"Entire account\" to create the project, `\u002Frepo:token`), or a publisher on https:\u002F\u002Fpypi.org\u002Fmanage\u002Faccount\u002Fpublishing\u002F (repository, workflow `pypi.yml`, environment `pypi`). A PyPI version can never be re-uploaded: fix a broken one with the next tag.\n\nActions blocked (billing): don't wait on a queued run, whose job can sit for minutes before the refusal shows in its annotations; `gh run cancel` it, so it cannot publish later, and publish from the machine. The repo stays untouched:\n```bash\ndir=\"$(mktemp -d ~\u002F.cache\u002Fpublish.XXXXXX)\"\ngit archive vX.Y.Z | tar -x -C \"$dir\"\ncd \"$dir\"                                              # then the backend directory, if any\nuv version --frozen X.Y.Z\nuv build --out-dir dist\nuvx --isolated --from dist\u002F*.whl \u003Ccommand> --version   # and --help of each area\nUV_PUBLISH_TOKEN=\"$(cat \u003Crepo root>\u002F.pypi\u002Ftoken)\" uv publish dist\u002F*\n```\nThen check the project's page as above and delete `$dir`. Token: only the repo's own `.pypi\u002F`, never printed. None: stop, `\u002Frepo:token`; another repo's only with the user's yes. Say in the report that this upload has no build provenance (`attest-build-provenance` runs only on GitHub). `pypi.yml` stays: budget back, the next tag publishes with provenance; meanwhile a failed run per tag is the only cost.\n\n## 9. Merge back, tidy\n```bash\ngit merge --no-ff release\u002FvX.Y.Z -m \"Merge branch 'release\u002FvX.Y.Z' into develop\"   # from develop\ngit push origin develop\ngit worktree remove .claude\u002Fworktrees\u002Frelease-vX.Y.Z\ngit branch -d release\u002FvX.Y.Z && git push origin --delete release\u002FvX.Y.Z\n```\nReport in the `repo` plugin's `debrief` format (`output-styles\u002Fdebrief.md`); a failed health probe or smoke test is a `Broken:` line.\n",{},"develop","e6de2f79fc1da5627cbf8370c3429680899389c4","plugins\u002Frepo\u002Fskills\u002Frelease","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo","https:\u002F\u002Fpypi.org\u002Fproject\u002Fkiln-cli\u002F","https:\u002F\u002Fgithub.com\u002Fantoine-tena","annski.fr","🚀 AI Eng | Multi-agent loops (LangGraph) | Observability: OpenTelemetry • Phoenix | Pres & Lead Dev @AnnSki - Django Ninja • Nuxt • Podman ","2026-11-15 05:35:20",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add antoine-tena\u002Fion-repo --skill release",{"tool":38,"command":39},"bunx","bunx skills add antoine-tena\u002Fion-repo --skill release",{"tool":41,"command":42},"pnpm","pnpm dlx skills add antoine-tena\u002Fion-repo --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Frelease\u002FSKILL.md",true,[],[47,54,61,68,75,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7EE5FTQ8BVEGXJ7MMBT262V","worktree","Create a work branch in a ready-to-use git worktree. The normal way to start a branch, so as not to cross another session in the main tree.","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Fworktree\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EE5CZ7CE9S93H7JK0WKD2T","update","Update ion-repo - the ion-repo tool of the machine and its plugins, then the open repo (ion repo update, on a branch merged right away into develop). Use when the user asks to update ion-repo, or accepts the update offered at session start.","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Fupdate\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EE59W4TMAZH6PB680GBRAK","token","Set up a service's credentials (PyPI, Stripe, an API, a host…) in a `.\u003Cservice>\u002F` folder at the repo root (`token`, chmod 600, and `config` on its scope), with one command that pastes the token unseen. Use when a task needs an API key or a token, or when the user wants to give one.","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Ftoken\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EE534SWGRB6H96DBVQ7Z06","statusline","Change the look of the status line - its style, its colors, among them the chat's (the person's and Claude's) - each shown before it is chosen. Use when the user wants another status line, other colors for it, or from `\u002Frepo:look`.","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7EE4WHZ80XRXHR226AFBNSA","skill","Write or sharpen a skill of an Ion tool's plugin - intent, SKILL.md in the right craft's plugin, one trigger case, docs; tested with `claude plugin eval` only on request. Use when the user wants a new skill, to fix one, or to check one fires and does its job.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Fskill\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Fskill\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7EE4TCY485ZC23XWTMFXQ78","review","https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Freview\u002FSKILL.md",[],[]]