Create a Changeset

Use this skill after implementation is complete and before committing a release-worthy change.

Workflow

1. Discover the repository's release rules

• Read the nearest AGENTS.md, CONTEXT.md, contributor guide, and release workflow that govern the work.
• Read git status --short, git diff HEAD --stat, and every relevant staged, unstaged, and untracked change.
• Locate .changeset/config.json, workspace manifests, package manifests, lockfiles, and the local Changesets CLI.
• Confirm that the repository uses Changesets. If its configuration or CLI is absent, report the blocker instead of creating a file.
• Resolve the repository's package manager from package.json and its lockfile. Use that manager for validation.
• Identify publishable package names and the repository's private-package rules. Use exact names from package.json.

Completion criterion: the Changesets setup, package manager, publishable packages, private-package policy, and complete change scope are known.

2. Classify impact and package ownership