[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FE8EEG42Z95804TK2KT89R":3,"skill-same:01M7FE8EEG42Z95804TK2KT89R":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FE8EEG42Z95804TK2KT89R","write-issue",null,"Files and moves issues on the repo's tracker (GitLab, GitHub or local files): one kind (bug, feature, chore) and one stage each, a title, the kind's template, and what each later stage needs. Use when filing, relabelling, moving or closing an issue, when work should be recorded instead of done now, or to split big work into child tickets.","Med-Karim-Ben-Boubaker\u002Fkarim-skills","Med-Karim-Ben-Boubaker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63352044?v=4","01M7FE4PT628J1M137P2SH4M5M","Karim Ben Boubaker","01M7FE4PV4JZRQT69G3TNBR5D0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: write-issue\ndescription: \"Files and moves issues on the repo's tracker (GitLab, GitHub or local files): one kind (bug, feature, chore) and one stage each, a title, the kind's template, and what each later stage needs. Use when filing, relabelling, moving or closing an issue, when work should be recorded instead of done now, or to split big work into child tickets.\"\n---\n\n# Write Issue\n\nEvery issue carries one **kind**, what it is, and one **stage**, what it needs next. The label strings are in the repo's `AGENTS.md` or `CLAUDE.md` under `### Issue labels`; the commands for this tracker (GitLab, GitHub or local files) are in `docs\u002Fagents\u002Fissue-tracker.md`. If either is missing, tell the user to run `\u002Fset-up-repo`.\n\n## Kinds and stages\n\n| Kind | Means |\n|---|---|\n| `bug` | Something works wrong |\n| `feature` | New or changed behaviour |\n| `chore` | Work with no change in behaviour: a refactor, infra, docs, a data run |\n\n| Stage | Needs next |\n|---|---|\n| `needs-triage` | Someone to decide its kind and stage |\n| `parked` | Nothing until it becomes a priority |\n| `needs-investigation` | The cause (bug) or the design (feature, chore) |\n| `needs-input` | An answer from a person outside the work: the reporter, a client, an expert |\n| `ready` | Building. The fix or design is written down with acceptance criteria |\n\nClosing is not a stage. Close as **done** (link the change, or where the behaviour already lives), **not planned** (say why), or **duplicate** (link the original). Work in progress shows as an assignee and a linked merge request, not a label. If only a human can build a `ready` issue, assign that person and say why in the brief.\n\n## Choose the stage\n\nSet the furthest stage you know is true. Use `needs-triage` only when you don't know, usually for an outside report or a quick capture.\n\n| Situation | Kind | Stage |\n|---|---|---|\n| \"A user says the export crashes; nobody has looked yet.\" | bug | `needs-triage` |\n| \"The export crashes on large files; I can reproduce it but don't know why.\" | bug | `needs-investigation` |\n| \"It crashes because the writer loads every row into memory; we'll stream it.\" | bug | `ready` |\n| \"Someone reports wrong dates, with no file attached.\" | bug | `needs-input`, waiting on the reporter |\n| \"We can't set the retention period until legal answers.\" | feature | `needs-input`, waiting on legal |\n| \"Dark mode would be nice someday.\" | feature | `parked` |\n| \"We need SSO this quarter but haven't designed it.\" | feature | `needs-investigation` |\n| \"SSO is specified.\" | feature | `ready` |\n| \"The staging database must move to the new server; it needs admin access.\" | chore | `ready`, assigned to the admin |\n| \"This is the crash reported in #42.\" | | Close as a duplicate of #42 |\n\n## Title\n\n- Bug: the symptom and where it shows. \"Export crashes on files over 50 MB.\"\n- Feature: what is true when it's done. \"Enterprise customers sign in with SSO.\"\n- Chore: the result, as a fact. \"Staging runs on the new database server.\"\n\nNever the fix, the issue number or a label: the tracker shows those beside the title.\n\n## The description grows\n\nFile the issue with its kind's template: [bug](templates\u002Fbug.md), [feature](templates\u002Ffeature.md), [chore](templates\u002Fchore.md). Fill what you know, and delete a section you have nothing for. A `needs-triage` issue may be free text.\n\nEach later stage **appends** sections to the description and never rewrites earlier ones, so the description reads as what was known at each point. Discussion goes in comments.\n\n| Moving to | Append |\n|---|---|\n| `parked` | `## Parked`: why not now, and what would make it a priority |\n| `needs-input` | A **comment**, not the description: who it waits on, the stage to return to, what is settled so far, and specific questions. If it waits on someone other than the reporter, offer the user `\u002Fwrite-questionnaire` and link its file |\n| `ready`, bug | `## Diagnosis`: the root cause, where it first goes wrong, and the check that goes red without the fix. Then `## Brief` |\n| `ready`, feature | `## Plan`: the chosen approach, or a link to the spec. Then `## Brief` |\n| `ready`, chore | `## Brief` |\n| closed | A comment with the reason, then close it as `docs\u002Fagents\u002Fissue-tracker.md` says |\n\n`## Brief` is the contract the builder works from: the desired behaviour, acceptance criteria as checkboxes, and what is out of scope. Write each criterion as something a person can see by running the software (a screen, a command's output, the rows a run writes), so the Demo in `\u002Freview-code` can prove it. Describe behaviour and interfaces, not file paths, which go stale.\n\nChange the stage label in the same step as the text, so the two always agree.\n\n## Split into children\n\nWhen a `ready` issue is too big for one change, keep it as the **parent** and split the work into child tickets as [SPLIT.md](SPLIT.md) says: native children of the parent (GitHub sub-issues, GitLab child tasks, files in the feature's `issues\u002F` folder) with blocking links between them, never loose issues. Each child gets the parent's kind and `ready`. The parent stays open until its last child closes. `\u002Fimplement-spec` then works the open, unblocked children in parallel.\n","# Write Issue\n\nEvery issue carries one **kind**, what it is, and one **stage**, what it needs next. The label strings are in the repo's `AGENTS.md` or `CLAUDE.md` under `### Issue labels`; the commands for this tracker (GitLab, GitHub or local files) are in `docs\u002Fagents\u002Fissue-tracker.md`. If either is missing, tell the user to run `\u002Fset-up-repo`.\n\n## Kinds and stages\n\n| Kind | Means |\n|---|---|\n| `bug` | Something works wrong |\n| `feature` | New or changed behaviour |\n| `chore` | Work with no change in behaviour: a refactor, infra, docs, a data run |\n\n| Stage | Needs next |\n|---|---|\n| `needs-triage` | Someone to decide its kind and stage |\n| `parked` | Nothing until it becomes a priority |\n| `needs-investigation` | The cause (bug) or the design (feature, chore) |\n| `needs-input` | An answer from a person outside the work: the reporter, a client, an expert |\n| `ready` | Building. The fix or design is written down with acceptance criteria |\n\nClosing is not a stage. Close as **done** (link the change, or where the behaviour already lives), **not planned** (say why), or **duplicate** (link the original). Work in progress shows as an assignee and a linked merge request, not a label. If only a human can build a `ready` issue, assign that person and say why in the brief.\n\n## Choose the stage\n\nSet the furthest stage you know is true. Use `needs-triage` only when you don't know, usually for an outside report or a quick capture.\n\n| Situation | Kind | Stage |\n|---|---|---|\n| \"A user says the export crashes; nobody has looked yet.\" | bug | `needs-triage` |\n| \"The export crashes on large files; I can reproduce it but don't know why.\" | bug | `needs-investigation` |\n| \"It crashes because the writer loads every row into memory; we'll stream it.\" | bug | `ready` |\n| \"Someone reports wrong dates, with no file attached.\" | bug | `needs-input`, waiting on the reporter |\n| \"We can't set the retention period until legal answers.\" | feature | `needs-input`, waiting on legal |\n| \"Dark mode would be nice someday.\" | feature | `parked` |\n| \"We need SSO this quarter but haven't designed it.\" | feature | `needs-investigation` |\n| \"SSO is specified.\" | feature | `ready` |\n| \"The staging database must move to the new server; it needs admin access.\" | chore | `ready`, assigned to the admin |\n| \"This is the crash reported in #42.\" | | Close as a duplicate of #42 |\n\n## Title\n\n- Bug: the symptom and where it shows. \"Export crashes on files over 50 MB.\"\n- Feature: what is true when it's done. \"Enterprise customers sign in with SSO.\"\n- Chore: the result, as a fact. \"Staging runs on the new database server.\"\n\nNever the fix, the issue number or a label: the tracker shows those beside the title.\n\n## The description grows\n\nFile the issue with its kind's template: [bug](templates\u002Fbug.md), [feature](templates\u002Ffeature.md), [chore](templates\u002Fchore.md). Fill what you know, and delete a section you have nothing for. A `needs-triage` issue may be free text.\n\nEach later stage **appends** sections to the description and never rewrites earlier ones, so the description reads as what was known at each point. Discussion goes in comments.\n\n| Moving to | Append |\n|---|---|\n| `parked` | `## Parked`: why not now, and what would make it a priority |\n| `needs-input` | A **comment**, not the description: who it waits on, the stage to return to, what is settled so far, and specific questions. If it waits on someone other than the reporter, offer the user `\u002Fwrite-questionnaire` and link its file |\n| `ready`, bug | `## Diagnosis`: the root cause, where it first goes wrong, and the check that goes red without the fix. Then `## Brief` |\n| `ready`, feature | `## Plan`: the chosen approach, or a link to the spec. Then `## Brief` |\n| `ready`, chore | `## Brief` |\n| closed | A comment with the reason, then close it as `docs\u002Fagents\u002Fissue-tracker.md` says |\n\n`## Brief` is the contract the builder works from: the desired behaviour, acceptance criteria as checkboxes, and what is out of scope. Write each criterion as something a person can see by running the software (a screen, a command's output, the rows a run writes), so the Demo in `\u002Freview-code` can prove it. Describe behaviour and interfaces, not file paths, which go stale.\n\nChange the stage label in the same step as the text, so the two always agree.\n\n## Split into children\n\nWhen a `ready` issue is too big for one change, keep it as the **parent** and split the work into child tickets as [SPLIT.md](SPLIT.md) says: native children of the parent (GitHub sub-issues, GitLab child tasks, files in the feature's `issues\u002F` folder) with blocking links between them, never loose issues. Each child gets the parent's kind and `ready`. The parent stays open until its last child closes. `\u002Fimplement-spec` then works the open, unblocked children in parallel.\n",{"name":5,"description":7},"main","03f9278801a451ca8b532ae5be7195296143861a","skills\u002Fwrite-issue",0,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker","https:\u002F\u002Fkarimbenboubaker.me\u002F","AI Engineer","2026-11-10 22:54:19",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill write-issue",{"tool":39,"command":40},"bunx","bunx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill write-issue",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill write-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002FSKILL.md",true,[47,53,57,61,65],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",103,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"SPLIT.md",4651,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002FSPLIT.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"templates\u002Fbug.md",669,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002Ftemplates\u002Fbug.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"templates\u002Fchore.md",166,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002Ftemplates\u002Fchore.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"templates\u002Ffeature.md",364,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002Ftemplates\u002Ffeature.md",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7FE8Y56P42CZS85V5NWGQ0B","write-walkthrough","Guide you through running a demo yourself that shows a fix or a new feature working: a few numbered steps in the chat, each a command to copy or a click to make, with what you should see.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-walkthrough\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7FE8SY1WVS77ZM15VSX9H08","write-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-spec\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7FE8Q2ZBJ61N6CEVFCVQPHR","write-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-questionnaire\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7FE8JMMVYP23YHD3KQ43SH4","write-pr","Writes a PR or MR from a fixed template: the tickets it closes, a summary sketch, before and after evidence that proves each acceptance criterion (screenshots for visible changes), and merge danger (one-way or two-way door, blast radius). Use when opening, writing or updating a pull request or merge request.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-pr\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7FE8AJW55TTN9R3KFHBC9T5","write-for-agents","How to write documents an agent reads: context pointers, information hierarchy, completion criteria, leading words and pruning, plus skill frontmatter and invocation mechanics. Use when creating or editing a skill, AGENTS.md, CLAUDE.md, or any doc an agent reaches through a pointer.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-for-agents\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7FE89234W1JQ5ZN3DKAVNN7","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[]]