Generate Changesets with Confidence in Multi-Package Repos

Where this fits

You're a maintainer of kimi-code, a multi-package repository with a published CLI and several internal packages. After merging a set of commits, you need to generate a changeset that accurately reflects what changed—and you can't afford to mistakenly include an internal package or miss a required major version confirmation. This skill automates that tedious, error-prone decision process.

Why agents benefit

• Inspects actual changes first: The agent runs git status and git diff --name-only to determine which packages were touched, instead of guessing from the prompt or commit messages.
• Enforces repository-specific rules: Knows that only @moonshot-ai/nori-code is published to the public, while other @moonshot-ai/* packages are internal—and that @moonshot-ai/pi-tui is a private fork that still gets a changelog.
• Handles bump levels and major confirmation: Automatically proposes the correct bump level (patch, minor, major) and explicitly asks for user confirmation before recording a major bump.
• Writes clear English changelog entries: Generates concise, user-facing phrasing that matches the project's style, avoiding vague or overly technical language.
• Prevents mixed-package changesets: Avoids grouping ignored packages with releasable ones in the frontmatter, which would break the changeset pipeline.

Practical scenarios

Hotfix to the CLI package

You've landed a small bugfix in @moonshot-ai/nori-code. The agent detects only that package changed, proposes a patch bump, and writes a changelog like "Fix: handle malformed arguments gracefully"—no internal packages touched.

Internal SDK update with no user-facing impact

Changes hit @moonshot-ai/nori-code-sdk but the CLI remains untouched. The agent recognizes the SDK is internal, flags it as unreleasable, and suggests either skipping the changeset or creating one with only the internal package for tracking—then confirms before proceeding.

Major version bump with an exception

A breaking change to the CLI requires a 2.0.0 release. The agent presents the change, asks for explicit confirmation, and also notes that @moonshot-ai/pi-tui (private fork) should get its own changelog entry, even though it's never published.

Add it to your agent workflow

Install the skill with:

npx skills add wangyuahn/nori-code --skill gen-changesets

Then, in your agent prompt:

Generate a changeset for the current branch. Inspect the diff, select the appropriate packages, and confirm the bump level.

The skill will guide the agent through the process, applying all core rules and formatting the output correctly.

Compare before adopting

When evaluating this skill, look beyond the 13 GitHub stars. Check how frequently the repository is updated, whether the author responds to issues, and if the skill has been adopted in other contexts. Also consider alternatives: generic changelog skills might not know your internal package structure, and manual generation is error-prone. Assess whether the skill's rules match your workflow, especially if you have unusual exceptions like pi-tui.

Why it is worth tracking

This skill encodes specialized domain knowledge that would otherwise be tribal. It demonstrates how a well-scoped skill can turn a tedious, mistake-prone task into a reliable agent step. With active community interest in multi-package release automation, this is a strong candidate to watch—evaluate it when your own changeset process starts causing friction or when you want to compare it against emerging alternatives. See the skill page for full details: https://www.openagentskill.com/skills/wangyuahn-gen-changesets