New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Gen Changesets

by MoonshotAI in MoonshotAI/kimi-code

A skill your agent uses 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.

MITAuto-check passedDevelopment

Install Gen Changesets

skills CLI
$ npx skills add MoonshotAI/kimi-code --skill gen-changesets -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MoonshotAI/kimi-code gen-changesets --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MoonshotAI/kimi-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gen-changesets .claude/skills/gen-changesets && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gen-changesets
GitHub stars
7.8k
Token cost
~1.1k tokens
SKILL.md length
604 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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.

  • Works in 5 steps: Whether to Write → What to Write → Bump Level → …
  • Generating changesets in the kimi-code repository — deciding whether to write one
  • SKILL.md covers 1. Whether to Write, 2. What to Write, 3. Bump Level and 4. Which Package, plus 1 more section
  • Calls git

What it does

Gen Changesets is an agent skill from MoonshotAI/kimi-code. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Kimi. The repository describes itself as: Kimi Code CLI — The Starting Point for Next-Gen Agents. The licence is MIT.

When your agent uses it

  • Generating changesets in the kimi-code repository — deciding whether to write one
  • Which package to list
  • The confirmation workflow

Example prompts

  • “/gen-changesets”

Requirements

  • A credential in YOUR_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Whether to Write
  2. What to Write
  3. Bump Level
  4. Which Package
  5. Workflow

What it can do on your machine

Read from SKILL.md and the folder at commit 0f052fe. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gen Changesets loads about 1.1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 604 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MoonshotAI/kimi-code at commit 0f052fe, republished under its MIT licence (© MoonshotAI). 604 words, ~1,076 tokens.

Download SKILL.mdSave it as .claude/skills/gen-changesets/SKILL.md (or your agent's skills folder).
name
gen-changesets
description
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.

Generate Changesets

The only user-facing published package is the CLI: @moonshot-ai/kimi-code. All other @moonshot-ai/* packages (sdk, kosong, kaos, oauth, telemetry, and so on) are internal.

1. Whether to Write

Rule 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.

Do not write:

  • Docs-only or tests-only changes that never enter the shipped artifact.
  • Changes internal to core/server packages — architecture, protocols, refactors, config/journal/wire mechanics — unless they fix a bug users care about.
  • When you are unsure whether users can perceive a change, ask first.

Do write: user-perceivable new features or behavior changes, and internal-package changes that fix a user-useful bug or change CLI output/behavior (list @moonshot-ai/kimi-code for those).

2. What to Write

Create a short kebab-case file under .changeset/:

markdown
---
"@moonshot-ai/kimi-code": patch
---

Fix occasional loss of tool call results in long conversations.

Wording:

  • One short, user-facing English sentence that states only what changed. Drop trailing clauses that explain the cause, the benefit, or the mechanism.
  • 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.
  • New features: say plainly what it is plus one line on how to use it, e.g. Add the /foo slash command to list active sessions. Run /foo to see them.
  • Experimental features: also state how to enable them (the flag, config key, or env var).
  • 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.
  • Internal packages' own changelogs (such as the sdk) are not curated for end users — write those entries honestly and technically.
  • One logical change per changeset; split unrelated changes into separate files.
Show full SKILL.md (269 more words)Show less

3. Bump Level

  • patch: bug fixes, small improvements, configuration additions to existing features — when in doubt, use this.
  • minor: a real new capability users could not do before (a new slash command, a new subcommand, a new mode).
  • 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.

4. Which Package

  • An internal change enters the CLI bundle and is user-perceivable → list @moonshot-ai/kimi-code.
  • An internal change does not enter the CLI or is not user-perceivable → write nothing; if it is written, list only that internal package.
  • Never mix packages ignored in .changeset/config.json with non-ignored packages in one frontmatter.
  • pi-tui exception: pi-tui-only changes list @moonshot-ai/pi-tui; if the same change is also visible to CLI users, write a separate CLI changeset (two files, never mixed).
  • kimi-inspect and the vis packages never appear in a changeset.

5. Workflow

  1. Run git status / git diff --name-only to see which packages actually changed.
  2. Apply section 1; if no changeset is needed, stop.
  3. Pick the package and the bump, and write the one sentence.
  4. Show the changeset text to whoever requested the work and get their confirmation before committing.
  5. 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.

Before a release, review the accumulated .changeset/ entries and delete the non-user-facing ones — the release PR regenerates from .changeset/ on main, so deleting a file removes its changelog entry without touching shipped code.

© MoonshotAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/gen-changesets of MoonshotAI/kimi-code.

Open the folder on GitHubat commit 0f052fe

Compare with similar skills

Gen Changesets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gen Changesets compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gen Changesets this skillMoonshotAI/kimi-code7.8k—~1.1kAutomated safety check: PassMIT
Ccmanager Configkbwo/ccmanager1.3k—~1.5kAutomated safety check: PassMIT
Pulse Releasequnqin24/Pulse516—~1.3kAutomated safety check: PassApache-2.0
Luvus ModuleRizRiyz/luvus957—~2.5kAutomated safety check: PassApache-2.0
Code Reviewtimwuhaotian/the-pair378—~250Automated safety check: PassMIT
DocSikao-Engine/KimiX114—~1.1kAutomated safety check: PassNone

Similar skills

  • Ccmanager Config

    kbwo/ccmanager

    Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

    1.3k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Pulse Release

    qunqin24/Pulse

    Release a new Pulse version end to end — checks, bilingual CHANGELOG entry, VERSION, tag, the release workflow, syncing main, and the issue replies that go with it.

    516 GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Luvus Module

    RizRiyz/luvus

    Write a luvus module (an extension for luvus, mission control for your AI coding agents).

    957 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Review

    timwuhaotian/the-pair

    Comprehensive code review with security and performance checks

    378 GitHub stars~250 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Doc

    Sikao-Engine/KimiX

    Guide for navigating and maintaining Kimix project documentation.

    114 GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Homerail PR Review

    xiaotianfotos/homerail

    Run HomeRail's built-in read-only pull request review DAG. An agent skill from xiaotianfotos/homerail.

    992 GitHub stars~670 tokensUpdated 12 days ago
    DevelopmentAuto-check passed

More from MoonshotAI/kimi-code

All 11 skills in this repo

  • Kimi Webbridge

    MoonshotAI/kimi-code

    Kimi Browser Extension（Kimi 浏览器扩展，原 Kimi WebBridge）lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login…

    7.8k GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Gen Docs

    MoonshotAI/kimi-code

    Update Kimi Code CLI user documentation after meaningful code changes that affect product behavior or user experience.

    7.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Kimi Datasource

    MoonshotAI/kimi-code

    Universal data-source assistant for stocks (Wind, S&P, SEC EDGAR), macro (World Bank, IMF, FRED, NBS), Chinese government data and standards (GB/HB/DB/TT), corporate, academic, legal, WHO/FAO/OECD…

    7.8k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Pre Changelog

    MoonshotAI/kimi-code

    Use before merging a kimi-code release PR to preview the user-facing CLI changelog in Chinese.

    7.8k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Review PR

    MoonshotAI/kimi-code

    在 kimi-code 仓库里 review 一个 PR 时使用：按 PR 模板逐节核对描述与 diff，并单独做一轮"回归与用户影响"评审，给出影响等级与评审摘要，评审摘要用用户当前使用的语言。

    7.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Write PR

    MoonshotAI/kimi-code

    在 kimi-code 仓库里创建或更新 PR 时使用：如何把 PR 模板的每一节写得简洁、便于 reviewer 理解，包括"行为变化与受影响人群"表。

    7.8k GitHub stars~909 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Gen Changesets

What does Gen Changesets do?

A skill your agent uses 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. Gen Changesets is an agent skill from MoonshotAI/kimi-code. 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.

When should I use Gen Changesets?

Gen Changesets fits situations like: generating changesets in the kimi-code repository — deciding whether to write one; which package to list; the confirmation workflow.

How do I install Gen Changesets in Claude Code?

Run `npx skills add MoonshotAI/kimi-code --skill gen-changesets -a claude-code`. Or copy the skill folder (.agents/skills/gen-changesets in MoonshotAI/kimi-code) into .claude/skills/gen-changesets in your project. Claude Code loads it when a task matches its description.

How do I install Gen Changesets in Codex?

Run `npx skills add MoonshotAI/kimi-code --skill gen-changesets -a codex`. Or copy the skill folder (.agents/skills/gen-changesets in MoonshotAI/kimi-code) into .agents/skills/gen-changesets in your project. Codex loads it when a task matches its description.

Can I use Gen Changesets in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MoonshotAI/kimi-code --skill gen-changesets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gen-changesets, .gemini/skills/gen-changesets, .github/skills/gen-changesets and .opencode/skills/gen-changesets in your project.

What does Gen Changesets need to run?

Going by SKILL.md and its folder, Gen Changesets needs the command-line tools its instructions call (git). Our summary lists: A credential in YOUR_API_KEY.

Does Gen Changesets access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Gen Changesets safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gen Changesets use?

Gen Changesets is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gen Changesets use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gen Changesets?

Skills that share tags, products or a category with Gen Changesets: Ccmanager Config (kbwo/ccmanager, 1.3k stars), Pulse Release (qunqin24/Pulse, 516 stars), Luvus Module (RizRiyz/luvus, 957 stars) and Code Review (timwuhaotian/the-pair, 378 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gen Changesets?

MoonshotAI (a GitHub organization) maintains it in MoonshotAI/kimi-code, which has 7,796 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: MoonshotAI/kimi-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.