[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7191HY9G0FKT7C44VQB79VR":3,"skill-same:01M7191HY9G0FKT7C44VQB79VR":59},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":8,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":21,"publishedAt":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7191HY9G0FKT7C44VQB79VR","changelog",null,"openplaybooks-dev\u002Fconverge","openplaybooks-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F270560357?v=4","01M7191G17AHW5SXN63HJ0BEZV","01M7191G29922BDNWN8CFVG4PD",3,"MIT","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fchangelog\u002FSKILL.md",[16],{"categoryNo":17,"categoryName":18,"taxonomyType":19,"taxonomyTypeDesc":20},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5],"2026-11-10 10:12:30",false,"---\nname: changelog\ndescription: Use when an RFC reaches `status: done` and a changelog entry needs to be written, when cutting a release version, when reviewing what changed since the last release, or when the user asks \"what's new\", \"write a changelog\", \"update the CHANGELOG\", or \"generate release notes\".\n---\n\n# Changelog — auto-generate from RFC metadata\n\n## Purpose\n\nEvery RFC that reaches `status: done` should produce a corresponding CHANGELOG.md entry. This skill ensures the changelog stays synchronized with shipped work without manual authoring.\n\n## When to invoke\n\nTrigger on:\n- \"Write a changelog entry for RFC XXXX\"\n- \"Update the to CHANGELOG.md\" after an RFC implementation\n- \"Cut a release\" \u002F \"what changed since last release?\"\n- An RFC's status transitions to `done`\n\n## Trigger on user messages like:\n- \"changelog\" \u002F \"write changelog\" \u002F \"update CHANGELOG.md\"\n- \"ship RFC 0034\" \u002F \"release v0.4.0\"\n- \"what's new since v0.3.0?\"\n\n## Do not invoke for:\n- Editing the changelog format or structure → edit CHANGELOG.md directly\n- Adding a new RFC → that's part of the RFC-writing workflow, not changelog\n\n## Workflow: RFC done → changelog entry\n\n### 1. Read the RFC frontmatter\n\nExtract from `docs\u002Frfcs\u002FNNNN-*.md`:\n\n```yaml\nrfc: 0034\ntitle: Ban depends_on; auto-chain tasks alphabetically within levels\nstatus: done\ntype: refactor          # feat | fix | refactor | chore | breaking\nsource: human\npriority_tier: tier1\nbackwards_compatible: no\nrisk: high\nbreaks_existing: yes\n```\n\n### 2. Map RFC type to CHANGELOG section\n\n| RFC `type` | CHANGELOG section |\n|---|---|\n| `feat` | `### Added` |\n| `fix` | `### Fixed` |\n| `refactor` | `### Changed` |\n| `chore` | `### Changed` |\n| `breaking` (or `breaks_existing: yes`) | `### Breaking` (always top) |\n\n### 3. Find related commits\n\n```bash\ngit log --oneline --grep=\"RFC 0034\" --grep=\"0034\" --grep=\"depends_on\" --all\n```\n\nUse commits to identify the key changes, but write the changelog entry from the RFC description, not the commit messages.\n\n### 4. Write the changelog entry\n\nFormat:\n```markdown\n- **RFC 0034**: Ban `depends_on` from TASK.md frontmatter. Tasks at the same directory level are now auto-chained alphabetically by ID. Migration: `converge migrate --rfc=0034`.\n```\n\nRules:\n- One bullet per RFC, under the appropriate section\n- Lead with the RFC number and title\n- Describe what changed for the user, not internal implementation details\n- Include migration instructions if `breaks_existing: yes`\n- Keep to 1-2 sentences max\n- Use backticks for code\u002Ffield names\n- End with a period\n\n### 5. Place under `[Unreleased]`\n\nInsert the entry under the correct section within `[Unreleased]`. If the section doesn't exist, create it. Sections order:\n\n```markdown\n## [Unreleased]\n\n### Breaking\n### Added\n### Changed\n### Fixed\n### Deprecated\n### Removed\n### Security\n```\n\n### 6. Update the RFC Progress table\n\nAdd a row to the RFC's Progress table:\n\n```markdown\n| Changelog entry | **done** | Added to CHANGELOG.md under [Unreleased] → Changed |\n```\n\n## CHANGELOG.md format\n\nThe file follows [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F):\n\n```markdown\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F),\nand this project adheres to [Semantic Versioning](https:\u002F\u002Fsemver.org\u002Fspec\u002Fv2.0.0.html).\n\n## [Unreleased]\n\n### Breaking\n\n### Added\n\n### Changed\n\n### Fixed\n\n## [0.3.0] - 2026-05-15\n\n### Added\n- Initial monorepo structure\n...\n```\n\n## Release cut workflow\n\nWhen the user says \"cut a release\" or \"release vX.Y.Z\":\n\n1. **Gather done RFCs** since last release:\n   ```bash\n   git log --oneline --since=\"2026-05-01\" -- docs\u002Frfcs\u002F\n   ```\n   Check which RFCs have `status: done` in their frontmatter.\n\n2. **Verify all done RFCs have changelog entries** — any missing, run the workflow above.\n\n3. **Replace `[Unreleased]` with versioned header**:\n   ```markdown\n   ## [0.4.0] - 2026-05-22\n   ```\n\n4. **Add new `[Unreleased]` section** above the versioned section.\n\n5. **Commit**:\n   ```\n   chore(release): v0.4.0\n\n   Changes since v0.3.0:\n   - RFC 0034: ...\n   - RFC 0033: ...\n   ```\n\n## File map\n\n```\n.claude\u002Fskills\u002Fchangelog\u002F\n  SKILL.md                    (this file — entry point and workflow)\n  reference\u002F\n    format.md                 (Keep a Changelog format reference)\n  templates\u002F\n    release-notes.md          (template for cutting releases)\nCHANGELOG.md                  (root — single source of truth)\ndocs\u002Frfcs\u002FNNNN-*.md           (RFC metadata source)\n```\n\n## Key rules\n\n1. **Never invent changelog entries** — every entry must map to a done RFC or a verified commit\n2. **User-facing language** — describe what changed for users, not internal refactors\n3. **One entry per RFC** — even if an RFC touches multiple files, it's one bullet\n4. **Breaking changes go first** — under `### Breaking` at the top of each version section\n5. **Include migration info** — if `breaks_existing: yes`, note how to migrate\n6. **Link to RFC** — reference the RFC number in the entry\n7. **Don't duplicate** — check if an entry already exists before adding\n","# Changelog — auto-generate from RFC metadata\n\n## Purpose\n\nEvery RFC that reaches `status: done` should produce a corresponding CHANGELOG.md entry. This skill ensures the changelog stays synchronized with shipped work without manual authoring.\n\n## When to invoke\n\nTrigger on:\n- \"Write a changelog entry for RFC XXXX\"\n- \"Update the to CHANGELOG.md\" after an RFC implementation\n- \"Cut a release\" \u002F \"what changed since last release?\"\n- An RFC's status transitions to `done`\n\n## Trigger on user messages like:\n- \"changelog\" \u002F \"write changelog\" \u002F \"update CHANGELOG.md\"\n- \"ship RFC 0034\" \u002F \"release v0.4.0\"\n- \"what's new since v0.3.0?\"\n\n## Do not invoke for:\n- Editing the changelog format or structure → edit CHANGELOG.md directly\n- Adding a new RFC → that's part of the RFC-writing workflow, not changelog\n\n## Workflow: RFC done → changelog entry\n\n### 1. Read the RFC frontmatter\n\nExtract from `docs\u002Frfcs\u002FNNNN-*.md`:\n\n```yaml\nrfc: 0034\ntitle: Ban depends_on; auto-chain tasks alphabetically within levels\nstatus: done\ntype: refactor          # feat | fix | refactor | chore | breaking\nsource: human\npriority_tier: tier1\nbackwards_compatible: no\nrisk: high\nbreaks_existing: yes\n```\n\n### 2. Map RFC type to CHANGELOG section\n\n| RFC `type` | CHANGELOG section |\n|---|---|\n| `feat` | `### Added` |\n| `fix` | `### Fixed` |\n| `refactor` | `### Changed` |\n| `chore` | `### Changed` |\n| `breaking` (or `breaks_existing: yes`) | `### Breaking` (always top) |\n\n### 3. Find related commits\n\n```bash\ngit log --oneline --grep=\"RFC 0034\" --grep=\"0034\" --grep=\"depends_on\" --all\n```\n\nUse commits to identify the key changes, but write the changelog entry from the RFC description, not the commit messages.\n\n### 4. Write the changelog entry\n\nFormat:\n```markdown\n- **RFC 0034**: Ban `depends_on` from TASK.md frontmatter. Tasks at the same directory level are now auto-chained alphabetically by ID. Migration: `converge migrate --rfc=0034`.\n```\n\nRules:\n- One bullet per RFC, under the appropriate section\n- Lead with the RFC number and title\n- Describe what changed for the user, not internal implementation details\n- Include migration instructions if `breaks_existing: yes`\n- Keep to 1-2 sentences max\n- Use backticks for code\u002Ffield names\n- End with a period\n\n### 5. Place under `[Unreleased]`\n\nInsert the entry under the correct section within `[Unreleased]`. If the section doesn't exist, create it. Sections order:\n\n```markdown\n## [Unreleased]\n\n### Breaking\n### Added\n### Changed\n### Fixed\n### Deprecated\n### Removed\n### Security\n```\n\n### 6. Update the RFC Progress table\n\nAdd a row to the RFC's Progress table:\n\n```markdown\n| Changelog entry | **done** | Added to CHANGELOG.md under [Unreleased] → Changed |\n```\n\n## CHANGELOG.md format\n\nThe file follows [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F):\n\n```markdown\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F),\nand this project adheres to [Semantic Versioning](https:\u002F\u002Fsemver.org\u002Fspec\u002Fv2.0.0.html).\n\n## [Unreleased]\n\n### Breaking\n\n### Added\n\n### Changed\n\n### Fixed\n\n## [0.3.0] - 2026-05-15\n\n### Added\n- Initial monorepo structure\n...\n```\n\n## Release cut workflow\n\nWhen the user says \"cut a release\" or \"release vX.Y.Z\":\n\n1. **Gather done RFCs** since last release:\n   ```bash\n   git log --oneline --since=\"2026-05-01\" -- docs\u002Frfcs\u002F\n   ```\n   Check which RFCs have `status: done` in their frontmatter.\n\n2. **Verify all done RFCs have changelog entries** — any missing, run the workflow above.\n\n3. **Replace `[Unreleased]` with versioned header**:\n   ```markdown\n   ## [0.4.0] - 2026-05-22\n   ```\n\n4. **Add new `[Unreleased]` section** above the versioned section.\n\n5. **Commit**:\n   ```\n   chore(release): v0.4.0\n\n   Changes since v0.3.0:\n   - RFC 0034: ...\n   - RFC 0033: ...\n   ```\n\n## File map\n\n```\n.claude\u002Fskills\u002Fchangelog\u002F\n  SKILL.md                    (this file — entry point and workflow)\n  reference\u002F\n    format.md                 (Keep a Changelog format reference)\n  templates\u002F\n    release-notes.md          (template for cutting releases)\nCHANGELOG.md                  (root — single source of truth)\ndocs\u002Frfcs\u002FNNNN-*.md           (RFC metadata source)\n```\n\n## Key rules\n\n1. **Never invent changelog entries** — every entry must map to a done RFC or a verified commit\n2. **User-facing language** — describe what changed for users, not internal refactors\n3. **One entry per RFC** — even if an RFC touches multiple files, it's one bullet\n4. **Breaking changes go first** — under `### Breaking` at the top of each version section\n5. **Include migration info** — if `breaks_existing: yes`, note how to migrate\n6. **Link to RFC** — reference the RFC number in the entry\n7. **Don't duplicate** — check if an entry already exists before adding\n",{},"main","7d618d8bc059f1a0974706d1d15ec25f73cf1e1d",".claude\u002Fskills\u002Fchangelog",1,"https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge","https:\u002F\u002Fplaybooks.to","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev","2026-06-13 10:11:21",{"source":7,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add openplaybooks-dev\u002Fconverge --skill changelog",{"tool":41,"command":42},"bunx","bunx skills add openplaybooks-dev\u002Fconverge --skill changelog",{"tool":44,"command":45},"pnpm","pnpm dlx skills add openplaybooks-dev\u002Fconverge --skill changelog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fchangelog\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"reference\u002Fformat.md","REFERENCE","参考文档",3559,"https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fchangelog\u002Freference\u002Fformat.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"templates\u002Frelease-notes.md",1389,"https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fchangelog\u002Ftemplates\u002Frelease-notes.md",[60,84,93,115,140,168],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":8,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":67,"publishedAt":22},"01M71989MQF3GPZ7P5TX6S93PD","hello-checker","Use this skill when asked to \"verify\", \"check\", or \"validate\" a file's existence and content. It provides a reliable workflow for confirming files meet their spec.","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002Ftests\u002Ftest-codex-real\u002F.converge\u002Fskills\u002Fhello-checker\u002FSKILL.md",[66],{"categoryNo":17,"categoryName":18,"taxonomyType":19,"taxonomyTypeDesc":20},[68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83],"checker","hello checker","hello","it","use","content","validate","spec","verify","check","file","workflow","when","Meet","files","for",{"skillNo":85,"name":86,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":8,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":90,"publishedAt":22},"01M7198823W79B3S15TPV97TCB","ask-skill","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002Ftests\u002Ftest-ask-autonomous\u002F.converge\u002Fplaybooks\u002Fdefault\u002Fskills\u002Fask-skill\u002FSKILL.md",[89],{"categoryNo":17,"categoryName":18,"taxonomyType":19,"taxonomyTypeDesc":20},[91,92],"ask skill","ask",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":8,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":103,"publishedAt":22},"01M71986EJ6VCM8YKGEM2YEDQV","html-review-artifact","Framework-wide guidance for crafting polished human-review artifacts as markdown or HTML","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002Fskills\u002Fhtml-review-artifact\u002FSKILL.md",[99,102],{"categoryNo":100,"categoryName":101,"taxonomyType":19,"taxonomyTypeDesc":20},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":17,"categoryName":18,"taxonomyType":19,"taxonomyTypeDesc":20},[104,105,106,107,108,83,109,110,111,112,113,114],"html","artifact","review","html review artifact","as","framework","wide","guidance","markdown","human","artifacts",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":8,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":22},"01M719833M2XWXG1VPBW30GW7J","converge-planning","Design a Converge playbook end-to-end. Use when the user says \"plan a project\", \"design a playbook\", \"decompose into tasks\", \"scaffold a Converge workflow\", \"onboard to Converge\", or asks how to write TASK.md \u002F playbook.yml. Two entry points: plan a new playbook or update an existing one. Hand off to `\u002Fconverge-control` after producing the playbook structure.","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002Fskills\u002Fconverge-planning\u002FSKILL.md",[121],{"categoryNo":17,"categoryName":18,"taxonomyType":19,"taxonomyTypeDesc":20},[123,124,125,126,79,127,72,128,129,130,131,132,133,134,135,136,137,138,139,80],"converge","converge planning","planning","structure","tasks","decompose","hand","write","plan","how","update","playbook","new","design","how to","end","project",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":8,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":152,"publishedAt":22},"01M7197XZT1T9GDYAJGVGX1J60","converge-control","Operate a Converge playbook end-to-end — start runs, monitor progress, narrow failures with `--select`, inspect runtime state, validate definitions, surgically reset subtrees, and stop stuck or orphaned runs. Use this skill whenever the user says \"run my playbook\", \"execute this\", \"monitor the run\", \"converge failed\", \"the run is stuck\", \"retry failures\", \"babysit this playbook\", \"what's the status?\", \"show me the gantt\", or asks how to use `converge run` \u002F `--select` \u002F `inspect` \u002F `doctor` \u002F `clean` \u002F `stop`. Also use it for `HTTP 401` \u002F `Invalid API key` failures on the first task — those are environment-not-playbook problems — and for any post-run cleanup work. Hand off to `converge-planning` if the user wants to design or restructure the playbook itself.","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002Fskills\u002Fconverge-control\u002FSKILL.md",[146,147],{"categoryNo":17,"categoryName":18,"taxonomyType":19,"taxonomyTypeDesc":20},{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[153,154,123,155,156,157,158,159,160,161,129,162,163,136,137,164,138,165,166,167],"converge control","control","operate","invalid","show","api","me","work","reset","show me","cleanup","clean","inspect","select","retry",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":8,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":22},"01M7197SCVN0QTD3CM4M83WYJH","repair-taskts","Fix task.ts definition issues — Seed syntax, missing .build(), empty checks, import errors, TypeScript errors","https:\u002F\u002Fgithub.com\u002Fopenplaybooks-dev\u002Fconverge\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Fsrc\u002Fnavigator\u002Frepair\u002Fskill-templates\u002Frepair-taskts\u002FSKILL.md",[174],{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},[176,177,178,179,130,180,181,182,183,184,185,186,187,188,189,138,190,123,191,192],"repair taskts","repair","Bash","edit","read","line","at","spawn","code","analysis","number","errors","issues","fix","chain","definition","never"]