[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EE4MS0BP19EXST991WC996":3,"skill-same:01M7EE4MS0BP19EXST991WC996":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},"01M7EE4MS0BP19EXST991WC996","report",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\u002Freport\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: report\ndescription: Report a defect of ion-repo (generated file, charter rule, plugin skill or hook, reusable workflow, command) to antoine-tena\u002Fion-repo: a PR when the fix is clear, an issue otherwise, only with the user's consent. Use when a problem comes from ion-repo ([REPORT-TO-ION-REPO]) or the user asks.\nargument-hint: \"[what went wrong]\"\n---\n\nWhat went wrong: `$ARGUMENTS`; without it, the defect met in this session.\n\nEverything this skill posts is **public**, under the user's GitHub account, and ion-repo is judged\nby its tracker: one clear, reproducible report is worth more than ten vague ones. Talk to the\nuser in their language; write the issue, the PR and its commits in **English**.\n\n## 1. Make sure it is ion-repo's\n\nIt is when the faulty thing comes from ion-repo: a file of the template (`.copier-answers.yml` at\nthe root, `_src_path` pointing to `antoine-tena\u002Fion-repo`), a rule of the shared part of\n`CLAUDE.md`, a skill, hook or the status line of an ion-repo plugin, a workflow or action called from `antoine-tena\u002Fion-repo`, the `ion-repo` or `charter`\ncommand. It is not when it is this repo's own code or rules (they are amended here), Claude\nCode itself (the user types `\u002Fbug`), or a third-party tool (uv, Copier, ruff, GitHub…), unless\nion-repo uses it wrongly.\n\nThen rule out an old version: `ion repo doctor` says whether the ion-repo tool (`ion-repo` line) and the\nrepo's template (`modèle` line) are behind the latest release. If they are, offer\n`\u002Frepo:update` first, then check whether the defect is still there.\n\n## 2. Search before writing\n\n    gh search issues --repo antoine-tena\u002Fion-repo --include-prs \"\u003Ctwo or three key words>\"\n\nOpen and closed, issues and PRs; try two or three wordings, in French too (older issues are).\n- An open issue or PR covers it: open nothing. Offer a 👍 on it\n  (`gh api -X POST repos\u002Fantoine-tena\u002Fion-repo\u002Fissues\u002F\u003Cn>\u002Freactions -f content=+1`), and a comment\n  only if it adds something (another stack, a smaller repro, a log).\n- A merged PR fixed it: the fix comes with the next release (`\u002Frepo:update`). A closed issue\n  turned it down: tell the user why. Post nothing in either case.\n\n## 3. Issue or pull request\n\n- **Pull request** when the fix is clear and local (a few lines in one place) and comes with\n  the test that would have caught it.\n- **Issue** when several approaches are possible, when the change would alter what every\n  generated repo receives (a new rule, file or dependency), or when the fix is unknown. In\n  doubt, the issue first: a PR built on a choice not made yet gets redone.\n\n## 4. Nothing private\n\nThis repo may be private: leave out its code, its name, its file names and paths, its data and\nURLs, and anything that looks like a secret, a token, an e-mail address or a real person's\ndata; write `~` for the home folder. The best evidence is a repro on a fresh repo, which also\nproves the defect is ion-repo's: `ion repo new \"$(mktemp -d)\u002Frepro\" --no-github` with the same stack\n(answers in `.copier-answers.yml`, flags in `ion repo new --help`), then the steps.\n\n## 5. Write it\n\nIssue. Title: what is wrong, specifically (`ion repo update drops the pnpm overrides of a nuxt\nrepo`, not `Bug in ion-repo`). Body: the sections of the bug form\n(`.github\u002FISSUE_TEMPLATE\u002Fbug.yml`), so that it reads like the others:\n\n    ### What happened?\n\n    What was run, what was expected, what happened instead; steps from `ion repo new` if possible.\n\n    ### Output\n\n    ```shell\n    the relevant lines only\n    ```\n\n    ### ion repo version\n\n    The `ion-repo` and `modèle` lines of `ion repo doctor`.\n\n    ### Stack\n\n    e.g. `django + nuxt, podman` (from `.copier-answers.yml`), or `n\u002Fa`.\n\n    ### OS\n\n    Linux, WSL, macOS or Other.\n\n    ### Claude Code version\n\n    `claude --version`, for a skill, hook or status line.\n\nAn improvement rather than a defect takes the sections of the idea form (`idea.yml`):\n`### What problem would this solve?`, then `### What do you have in mind?`. Last line of the\nbody: `\u003Csub>Drafted with Claude Code (\u002Frepo:report).\u003C\u002Fsub>`.\n\nPull request: the sections of `.github\u002Fpull_request_template.md` (What, Why, How to test,\nChecklist), `Closes #\u003Cn>` when an issue exists, the output of the checks, and the same last\nline.\n\n## 6. Ask, then post\n\nShow the user the title and the whole body (for a PR, the diff too), say that it will be\npublic under their GitHub account, and post only after an explicit yes. A no ends it: nothing\nis posted, and it is not brought up again.\n\n**Issue**, with `gh` logged in (`gh auth status`):\n\n    gh issue create --repo antoine-tena\u002Fion-repo --title \"\u003Ctitle>\" --body-file \u003Cfile>\n\nNo `--label`: the maintainer labels at triage. Without `gh`, give the user the prefilled form\ninstead, each value URL-encoded:\n`https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fissues\u002Fnew?template=bug.yml&title=…&what=…&output=…&version=…&stack=…&claude-code=…`.\n\n**Pull request.** If `gh api user --jq .login` prints `antoine-tena`, the user is ion-repo's\nmaintainer: no fork, no PR, the fix goes into their ion-repo checkout following its `CLAUDE.md`.\nAnyone else:\n1. Outside this repo, in a temporary folder: `git clone https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo`,\n   then `git switch -c fix\u002F\u003Cshort-name>` (the clone starts on `develop`).\n2. Read the clone's `CLAUDE.md` and `CONTRIBUTING.md`: for this work they replace the rules of\n   the user's repo (branches, commits, checks).\n3. The smallest change that fixes it, and the test that would have caught it. `uv sync`, then\n   the checks of `CONTRIBUTING.md`: all must pass. If they fail for a reason you cannot see,\n   open an issue instead, with what you found.\n4. Commits: `fix: …` title of 50 characters at most, no `Co-Authored-By: Claude` or\n   `Claude-Session:` trailer, no `--author`.\n5. After the yes: `gh repo fork --remote` (the fork becomes `origin`, ion-repo `upstream`),\n   `git push -u origin fix\u002F\u003Cshort-name>`, then\n   `gh pr create --repo antoine-tena\u002Fion-repo --base develop --head \u003Clogin>:fix\u002F\u003Cshort-name> --title \"\u003Ctitle>\" --body-file \u003Cfile>`.\n\n## 7. After\n\nGive the link. The fix reaches this repo with the next ion-repo release (`\u002Frepo:update`, or the\nprompt at the start of a session). Meanwhile ion-repo's files in this repo stay as they are\n([REPORT-TO-ION-REPO]); if the defect blocks the user, a workaround that does not touch them (a\nsetting, a command run by hand) is fine, and worth a line in the issue.\n\nOne defect per issue, one issue per defect; no `@` mention of the maintainer (they watch the\nrepo); never more than one comment or reaction on the same issue.\n","What went wrong: `$ARGUMENTS`; without it, the defect met in this session.\n\nEverything this skill posts is **public**, under the user's GitHub account, and ion-repo is judged\nby its tracker: one clear, reproducible report is worth more than ten vague ones. Talk to the\nuser in their language; write the issue, the PR and its commits in **English**.\n\n## 1. Make sure it is ion-repo's\n\nIt is when the faulty thing comes from ion-repo: a file of the template (`.copier-answers.yml` at\nthe root, `_src_path` pointing to `antoine-tena\u002Fion-repo`), a rule of the shared part of\n`CLAUDE.md`, a skill, hook or the status line of an ion-repo plugin, a workflow or action called from `antoine-tena\u002Fion-repo`, the `ion-repo` or `charter`\ncommand. It is not when it is this repo's own code or rules (they are amended here), Claude\nCode itself (the user types `\u002Fbug`), or a third-party tool (uv, Copier, ruff, GitHub…), unless\nion-repo uses it wrongly.\n\nThen rule out an old version: `ion repo doctor` says whether the ion-repo tool (`ion-repo` line) and the\nrepo's template (`modèle` line) are behind the latest release. If they are, offer\n`\u002Frepo:update` first, then check whether the defect is still there.\n\n## 2. Search before writing\n\n    gh search issues --repo antoine-tena\u002Fion-repo --include-prs \"\u003Ctwo or three key words>\"\n\nOpen and closed, issues and PRs; try two or three wordings, in French too (older issues are).\n- An open issue or PR covers it: open nothing. Offer a 👍 on it\n  (`gh api -X POST repos\u002Fantoine-tena\u002Fion-repo\u002Fissues\u002F\u003Cn>\u002Freactions -f content=+1`), and a comment\n  only if it adds something (another stack, a smaller repro, a log).\n- A merged PR fixed it: the fix comes with the next release (`\u002Frepo:update`). A closed issue\n  turned it down: tell the user why. Post nothing in either case.\n\n## 3. Issue or pull request\n\n- **Pull request** when the fix is clear and local (a few lines in one place) and comes with\n  the test that would have caught it.\n- **Issue** when several approaches are possible, when the change would alter what every\n  generated repo receives (a new rule, file or dependency), or when the fix is unknown. In\n  doubt, the issue first: a PR built on a choice not made yet gets redone.\n\n## 4. Nothing private\n\nThis repo may be private: leave out its code, its name, its file names and paths, its data and\nURLs, and anything that looks like a secret, a token, an e-mail address or a real person's\ndata; write `~` for the home folder. The best evidence is a repro on a fresh repo, which also\nproves the defect is ion-repo's: `ion repo new \"$(mktemp -d)\u002Frepro\" --no-github` with the same stack\n(answers in `.copier-answers.yml`, flags in `ion repo new --help`), then the steps.\n\n## 5. Write it\n\nIssue. Title: what is wrong, specifically (`ion repo update drops the pnpm overrides of a nuxt\nrepo`, not `Bug in ion-repo`). Body: the sections of the bug form\n(`.github\u002FISSUE_TEMPLATE\u002Fbug.yml`), so that it reads like the others:\n\n    ### What happened?\n\n    What was run, what was expected, what happened instead; steps from `ion repo new` if possible.\n\n    ### Output\n\n    ```shell\n    the relevant lines only\n    ```\n\n    ### ion repo version\n\n    The `ion-repo` and `modèle` lines of `ion repo doctor`.\n\n    ### Stack\n\n    e.g. `django + nuxt, podman` (from `.copier-answers.yml`), or `n\u002Fa`.\n\n    ### OS\n\n    Linux, WSL, macOS or Other.\n\n    ### Claude Code version\n\n    `claude --version`, for a skill, hook or status line.\n\nAn improvement rather than a defect takes the sections of the idea form (`idea.yml`):\n`### What problem would this solve?`, then `### What do you have in mind?`. Last line of the\nbody: `\u003Csub>Drafted with Claude Code (\u002Frepo:report).\u003C\u002Fsub>`.\n\nPull request: the sections of `.github\u002Fpull_request_template.md` (What, Why, How to test,\nChecklist), `Closes #\u003Cn>` when an issue exists, the output of the checks, and the same last\nline.\n\n## 6. Ask, then post\n\nShow the user the title and the whole body (for a PR, the diff too), say that it will be\npublic under their GitHub account, and post only after an explicit yes. A no ends it: nothing\nis posted, and it is not brought up again.\n\n**Issue**, with `gh` logged in (`gh auth status`):\n\n    gh issue create --repo antoine-tena\u002Fion-repo --title \"\u003Ctitle>\" --body-file \u003Cfile>\n\nNo `--label`: the maintainer labels at triage. Without `gh`, give the user the prefilled form\ninstead, each value URL-encoded:\n`https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fissues\u002Fnew?template=bug.yml&title=…&what=…&output=…&version=…&stack=…&claude-code=…`.\n\n**Pull request.** If `gh api user --jq .login` prints `antoine-tena`, the user is ion-repo's\nmaintainer: no fork, no PR, the fix goes into their ion-repo checkout following its `CLAUDE.md`.\nAnyone else:\n1. Outside this repo, in a temporary folder: `git clone https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo`,\n   then `git switch -c fix\u002F\u003Cshort-name>` (the clone starts on `develop`).\n2. Read the clone's `CLAUDE.md` and `CONTRIBUTING.md`: for this work they replace the rules of\n   the user's repo (branches, commits, checks).\n3. The smallest change that fixes it, and the test that would have caught it. `uv sync`, then\n   the checks of `CONTRIBUTING.md`: all must pass. If they fail for a reason you cannot see,\n   open an issue instead, with what you found.\n4. Commits: `fix: …` title of 50 characters at most, no `Co-Authored-By: Claude` or\n   `Claude-Session:` trailer, no `--author`.\n5. After the yes: `gh repo fork --remote` (the fork becomes `origin`, ion-repo `upstream`),\n   `git push -u origin fix\u002F\u003Cshort-name>`, then\n   `gh pr create --repo antoine-tena\u002Fion-repo --base develop --head \u003Clogin>:fix\u002F\u003Cshort-name> --title \"\u003Ctitle>\" --body-file \u003Cfile>`.\n\n## 7. After\n\nGive the link. The fix reaches this repo with the next ion-repo release (`\u002Frepo:update`, or the\nprompt at the start of a session). Meanwhile ion-repo's files in this repo stay as they are\n([REPORT-TO-ION-REPO]); if the defect blocks the user, a workaround that does not touch them (a\nsetting, a command run by hand) is fine, and worth a line in the issue.\n\nOne defect per issue, one issue per defect; no `@` mention of the maintainer (they watch the\nrepo); never more than one comment or reaction on the same issue.\n",{},"develop","e6de2f79fc1da5627cbf8370c3429680899389c4","plugins\u002Frepo\u002Fskills\u002Freport","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 report",{"tool":38,"command":39},"bunx","bunx skills add antoine-tena\u002Fion-repo --skill report",{"tool":41,"command":42},"pnpm","pnpm dlx skills add antoine-tena\u002Fion-repo --skill report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fantoine-tena\u002Fion-repo\u002Fblob\u002Fdevelop\u002Fplugins\u002Frepo\u002Fskills\u002Freport\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",[],[]]