agentleFS
Sign inStart free
MoonshotAIMoonshotAI/kimi-cli/.agents/skills/gen-changelog/SKILL.md

gen-changelog

Skill11k starsChanged 41 days agoApache-2.0Archived repositoryView on GitHub

Generate changelog entries for code changes.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Breaking changes: if any, add a section under ## Unreleased in docs/en/release-notes/breaking-changes.md with Affected + Migration …

    line 14
  2. Very specific:

    User-meaningful only: No internal refactors, test churn, or CI tweaks — except Lib: for SDK-facing changes.

    line 25
  3. Distinctive:

    When unsure, match an existing entry of the same kind.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generate changelog entries for changes on the current branch relative to main, then sync to the docs site.

Steps

  1. Inspect: git log main..HEAD --oneline + git diff main..HEAD --stat.
  2. Edit root CHANGELOG: add bullets under ## Unreleased in CHANGELOG.md using the prefix table below. For changes scoped to a subpackage under packages/ or sdks/, also update that subpackage's CHANGELOG.md — subpackage CHANGELOGs follow their own prefix conventions (e.g. packages/kosong/CHANGELOG.md uses provider prefixes like Kimi: / Anthropic:); only the root CHANGELOG follows the table below.
  3. Sync English docs: node docs/scripts/sync-changelog.mjs.
  4. Translate to Chinese: hand-write equivalents under ## 未发布 in docs/zh/release-notes/changelog.md. Use the full-width colon ：. Follow docs/AGENTS.md terminology.
  5. Breaking changes: if any, add a section under ## Unreleased in docs/en/release-notes/breaking-changes.md with Affected + Migration subsections, and under ## 未发布 in docs/zh/release-notes/breaking-changes.md with 受影响 + 迁移 subsections.

Entry format

- <Prefix>: <verb-led sentence, readable standalone> — <optional rationale / before-after / migration>
  • First sentence stands alone — readers should know after one sentence whether the bullet matters to them.
  • One change per bullet. No ; also, ; and, or nested em-dashes. Two changes = two bullets.
  • Verb-led: Fix … / Add … / Switch … / Bump ….
  • User-meaningful only. No internal refactors, test churn, or CI tweaks — except Lib: for SDK-facing changes.

Prefixes — pick from this list, do not invent new ones

PrefixScope
ShellInteractive TUI: keys, status bar, slash commands, terminal rendering
Webkimi web
Viskimi vis tracing visualizer
CLITop-level flags, subcommands, --print / --yolo / --afk
ACPZed / JetBrains and other ACP integrations
CoreAgent runtime, step loop, approval, quota, turns, background tasks
ToolAny built-in tool; name the specific tool in the body (ReadFile, Grep, Todo, Plan, …)
SkillSkill discovery/loading, Flow, Loop (always singular — not Skills:)
MCPMCP server integration
PluginPlugin system, kimi plugin subcommands
LLMProvider-agnostic or cross-provider; name the provider in the body (Kimi / Anthropic / OpenAI / DeepSeek …). Do not create per-provider prefixes
KosongChanges to the kosong LLM abstraction layer surfaced in the root CHANGELOG (the subpackage's own CHANGELOG uses provider prefixes)
WireWire protocol events, version
AuthOAuth, token refresh, /login
ConfigConfig schema, env vars
LibSDK-facing API changes
BuildNix / Rust / Python / packaging

When unsure, match an existing entry of the same kind. Prefer this list; if you genuinely need a new prefix, raise it with maintainers and update this table in the same PR so the convention stays single-sourced.

Ordering: within each version, group bullets by prefix in the order of the table above. Order within a prefix is free — keep the development order.

Highlights

Starting from the next release, add **Highlights**: … under each version header (1–3 items most users will notice); mirror it as **亮点**：… in Chinese. Skip on releases that are only internal or Lib:. Highlights summarize — every highlighted item still needs its full bullet below. Do not backfill historical versions.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. UniClipboard/UniClipboard★ 2ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free