[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ESD8NSW60P4GVSESVA0AX":3,"skill-same:01M74ESD8NSW60P4GVSESVA0AX":47},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M74ESD8NSW60P4GVSESVA0AX","gen-changesets",null,"Use when generating changesets in the kimi-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.","MoonshotAI\u002Fkimi-code","MoonshotAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129152888?v=4","01M74ERZMTV9BR82QKWAF5NAVA","Moonshot AI","01M74ERZND3KECTZ02YW0FYJSR",8226,"MIT","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgen-changesets\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: gen-changesets\ndescription: Use when generating changesets in the kimi-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.\n---\n\n# Generate Changesets\n\nThe only user-facing published package is the CLI: `@moonshot-ai\u002Fkimi-code`. All other `@moonshot-ai\u002F*` packages (sdk, oauth, telemetry, and so on) are internal.\n\n## 1. Whether to Write\n\nRule of thumb: **if users cannot perceive the change, write no changeset.** A changeset is a user-facing changelog entry, not a shipping gate — internal changes merged to main ship with the next release anyway, so skipping loses nothing.\n\nDo not write:\n- Docs-only or tests-only changes that never enter the shipped artifact.\n- Changes internal to core\u002Fserver packages — architecture, protocols, refactors, config\u002Fjournal\u002Fwire mechanics — unless they fix a bug users care about.\n- When you are unsure whether users can perceive a change, ask first.\n\nDo write: user-perceivable new features or behavior changes, and internal-package changes that fix a user-useful bug or change CLI output\u002Fbehavior (list `@moonshot-ai\u002Fkimi-code` for those).\n\n## 2. What to Write\n\nCreate a short kebab-case file under `.changeset\u002F`:\n\n```markdown\n---\n\"@moonshot-ai\u002Fkimi-code\": patch\n---\n\nFix occasional loss of tool call results in long conversations.\n```\n\nWording:\n- One short, user-facing English sentence that states only what changed. Drop trailing clauses that explain the cause, the benefit, or the mechanism.\n- When a default flips or an existing behavior is removed, name the behavior users lose, not only the new default. State the escape hatch if one exists, e.g. `Stop hot-reloading config, skills, and AGENTS.md by default; set [watch] enabled = true or KIMI_CODE_WATCH=1 to turn it back on.`; if there is none, say plainly that the old behavior is no longer available.\n- New features: say plainly what it is plus one line on how to use it, e.g. `Add the \u002Ffoo slash command to list active sessions. Run \u002Ffoo to see them.`\n- Experimental features: also state how to enable them (the flag, config key, or env var).\n- No file, class, or function names, and no PR numbers. No vague words like refactor, optimize, or improve. No real internal identifiers — use neutral placeholders such as `example.com` or `YOUR_API_KEY`.\n- Internal packages' own changelogs (such as the sdk) are not curated for end users — write those entries honestly and technically.\n- One logical change per changeset; split unrelated changes into separate files.\n\n## 3. Bump Level\n\n- `patch`: bug fixes, small improvements, configuration additions to existing features — when in doubt, use this.\n- `minor`: a real new capability users could not do before (a new slash command, a new subcommand, a new mode).\n- `major`: **never write it.** If you think a change qualifies, stop and ask the user; without explicit approval fall back to `minor`, or to `patch` if `minor` is also unclear.\n\n## 4. Which Package\n\n- An internal change enters the CLI bundle and is user-perceivable → list `@moonshot-ai\u002Fkimi-code`.\n- An internal change does not enter the CLI or is not user-perceivable → write nothing; if it is written, list only that internal package.\n- Never mix packages ignored in `.changeset\u002Fconfig.json` with non-ignored packages in one frontmatter.\n- pi-tui exception: pi-tui-only changes list `@moonshot-ai\u002Fpi-tui`; if the same change is also visible to CLI users, write a separate CLI changeset (two files, never mixed).\n- The vis packages never appear in a changeset.\n\n## 5. Workflow\n\n1. Run `git status` \u002F `git diff --name-only` to see which packages actually changed.\n2. Apply section 1; if no changeset is needed, stop.\n3. Pick the package and the bump, and write the one sentence.\n4. **Show the changeset text to whoever requested the work and get their confirmation before committing.**\n5. Do not guess at changes you do not understand: finish the parts that are clear, then list what is unclear and ask whether you may dig into the code.\n\nBefore a release, review the accumulated `.changeset\u002F` entries and delete the non-user-facing ones — the release PR regenerates from `.changeset\u002F` on the selected release branch, so deleting a file removes its changelog entry without touching shipped code.\n","# Generate Changesets\n\nThe only user-facing published package is the CLI: `@moonshot-ai\u002Fkimi-code`. All other `@moonshot-ai\u002F*` packages (sdk, oauth, telemetry, and so on) are internal.\n\n## 1. Whether to Write\n\nRule of thumb: **if users cannot perceive the change, write no changeset.** A changeset is a user-facing changelog entry, not a shipping gate — internal changes merged to main ship with the next release anyway, so skipping loses nothing.\n\nDo not write:\n- Docs-only or tests-only changes that never enter the shipped artifact.\n- Changes internal to core\u002Fserver packages — architecture, protocols, refactors, config\u002Fjournal\u002Fwire mechanics — unless they fix a bug users care about.\n- When you are unsure whether users can perceive a change, ask first.\n\nDo write: user-perceivable new features or behavior changes, and internal-package changes that fix a user-useful bug or change CLI output\u002Fbehavior (list `@moonshot-ai\u002Fkimi-code` for those).\n\n## 2. What to Write\n\nCreate a short kebab-case file under `.changeset\u002F`:\n\n```markdown\n---\n\"@moonshot-ai\u002Fkimi-code\": patch\n---\n\nFix occasional loss of tool call results in long conversations.\n```\n\nWording:\n- One short, user-facing English sentence that states only what changed. Drop trailing clauses that explain the cause, the benefit, or the mechanism.\n- When a default flips or an existing behavior is removed, name the behavior users lose, not only the new default. State the escape hatch if one exists, e.g. `Stop hot-reloading config, skills, and AGENTS.md by default; set [watch] enabled = true or KIMI_CODE_WATCH=1 to turn it back on.`; if there is none, say plainly that the old behavior is no longer available.\n- New features: say plainly what it is plus one line on how to use it, e.g. `Add the \u002Ffoo slash command to list active sessions. Run \u002Ffoo to see them.`\n- Experimental features: also state how to enable them (the flag, config key, or env var).\n- No file, class, or function names, and no PR numbers. No vague words like refactor, optimize, or improve. No real internal identifiers — use neutral placeholders such as `example.com` or `YOUR_API_KEY`.\n- Internal packages' own changelogs (such as the sdk) are not curated for end users — write those entries honestly and technically.\n- One logical change per changeset; split unrelated changes into separate files.\n\n## 3. Bump Level\n\n- `patch`: bug fixes, small improvements, configuration additions to existing features — when in doubt, use this.\n- `minor`: a real new capability users could not do before (a new slash command, a new subcommand, a new mode).\n- `major`: **never write it.** If you think a change qualifies, stop and ask the user; without explicit approval fall back to `minor`, or to `patch` if `minor` is also unclear.\n\n## 4. Which Package\n\n- An internal change enters the CLI bundle and is user-perceivable → list `@moonshot-ai\u002Fkimi-code`.\n- An internal change does not enter the CLI or is not user-perceivable → write nothing; if it is written, list only that internal package.\n- Never mix packages ignored in `.changeset\u002Fconfig.json` with non-ignored packages in one frontmatter.\n- pi-tui exception: pi-tui-only changes list `@moonshot-ai\u002Fpi-tui`; if the same change is also visible to CLI users, write a separate CLI changeset (two files, never mixed).\n- The vis packages never appear in a changeset.\n\n## 5. Workflow\n\n1. Run `git status` \u002F `git diff --name-only` to see which packages actually changed.\n2. Apply section 1; if no changeset is needed, stop.\n3. Pick the package and the bump, and write the one sentence.\n4. **Show the changeset text to whoever requested the work and get their confirmation before committing.**\n5. Do not guess at changes you do not understand: finish the parts that are clear, then list what is unclear and ask whether you may dig into the code.\n\nBefore a release, review the accumulated `.changeset\u002F` entries and delete the non-user-facing ones — the release PR regenerates from `.changeset\u002F` on the selected release branch, so deleting a file removes its changelog entry without touching shipped code.\n",{"name":5,"description":7},"main","54a9e51fcb0531c4dff816e492a8e6d0a598641e",".agents\u002Fskills\u002Fgen-changesets",1377,"https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code","https:\u002F\u002Fwww.kimi.com\u002Fcode\u002Fdocs\u002F","https:\u002F\u002Fgithub.com\u002FMoonshotAI","https:\u002F\u002Fmoonshot.ai","2026-11-14 19:55:03",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add MoonshotAI\u002Fkimi-code --skill gen-changesets",{"tool":39,"command":40},"bunx","bunx skills add MoonshotAI\u002Fkimi-code --skill gen-changesets",{"tool":42,"command":43},"pnpm","pnpm dlx skills add MoonshotAI\u002Fkimi-code --skill gen-changesets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgen-changesets\u002FSKILL.md",true,[],[48,55,61,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M74ETAEBHZ0QS6Y4BT29PKNF","golden-skill","Golden fixture skill","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fmigration-legacy\u002Ftest\u002Ffixtures\u002Fgolden\u002F.kimi\u002Fskills\u002Fgolden-skill\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M74ET9QF6YK6KD5KM2W4XPBD","tools","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Ftools\u002Fskill.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M74ET7K1MXGBYV91558T1VMC","review","Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Freview\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M74ET2KQ5CC4JCFGBSG0YXM3","consolidate","Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Fconsolidate\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M74ET036WTFZ4XH9KC2M84KQ","sub-skill","Discover and reorganize the skill inventory into hierarchical sub-skill bundles. Use when the user asks to review, group, or consolidate skills into a parent bundle.","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74ESXAT6AX5YG29SN3WY83J","write-tui","Use when writing or modifying the kimi-code terminal UI in apps\u002Fkimi-code\u002Fsrc\u002Ftui — components, dialogs\u002Fselectors, slash commands, themes, streaming render, or the KimiTUI controllers. Covers the architecture, where new features go, test placement, the theme system mechanics, and the dialog interaction\u002Fvisual spec (DESIGN.md).","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-tui\u002FSKILL.md",[],[]]