Skill

status

Provides awareness of existing changeset files when working in .changeset/. Loads context about pending changesets to prevent duplicates and inform decisions about new changesets. Activates when reading or listing files in the .changeset/ directory, reviewing pending changes, or discussing release readiness.

npx claudepluginhub savvy-web/systems --plugin changesets

Tool Access

This skill uses the workspace's default tool permissions.

Preview

When working with changesets, be aware of what already exists to avoid duplicates and conflicts.

SKILL.md

Similar Skills

angular-new-app

100.1k

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

angular-developer

100.1k

Generates Angular code and provides architectural guidance for projects, components, services, reactivity with signals, forms, dependency injection, routing, SSR, ARIA accessibility, animations, Tailwind styling, testing, and CLI tooling.

20 files

angular-angular-1

ui-ux-pro-max

70.8k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 23, 2026

Actions

View Source View Plugin View on GitHub View README

status

Changeset Status Awareness

When working with changesets, be aware of what already exists to avoid duplicates and conflicts.

Check Before Creating

Before creating a new changeset file, always check for existing ones:

List all .md files in .changeset/ (excluding README.md)

Read each existing changeset to understand which packages and bump types are already covered

Compare the intended new changeset content against existing ones before proceeding

Avoid Duplicate Entries

If an existing changeset already covers the same package and change type as the one you intend to create:

Do not create a new changeset file for that package/bump-type combination

Instead, suggest updating the existing changeset using /changesets:update

Only create a new changeset when the package or bump type is not yet represented, or when the changes are clearly distinct enough to warrant separate entries

Summarize When Listing or Reviewing

When listing or reviewing the current set of changesets, always include:

The total number of pending changesets

Any packages that appear in more than one changeset, noting which bump types are involved

This helps identify consolidation opportunities and ensures nothing is accidentally duplicated before a release.

Available Management Skills

Use these skills to manage pending changesets:

/changesets:list — overview of pending changesets with packages, bump types, and content previews

/changesets:update — modify an existing changeset's content or bump type

/changesets:merge — combine changesets that share the same bump type into a single file

/changesets:delete — remove a changeset that is no longer needed

/changesets:preview — preview the combined CHANGELOG output that the current set of changesets would produce

Changeset Status Awareness

When working with changesets, be aware of what already exists to avoid duplicates and conflicts.

Check Before Creating

Before creating a new changeset file, always check for existing ones:

List all .md files in .changeset/ (excluding README.md)
Read each existing changeset to understand which packages and bump types are already covered
Compare the intended new changeset content against existing ones before proceeding

Avoid Duplicate Entries

If an existing changeset already covers the same package and change type as the one you intend to create:

Do not create a new changeset file for that package/bump-type combination
Instead, suggest updating the existing changeset using /changesets:update
Only create a new changeset when the package or bump type is not yet represented, or when the changes are clearly distinct enough to warrant separate entries

Summarize When Listing or Reviewing

When listing or reviewing the current set of changesets, always include:

The total number of pending changesets
Any packages that appear in more than one changeset, noting which bump types are involved

This helps identify consolidation opportunities and ensures nothing is accidentally duplicated before a release.

Available Management Skills

Use these skills to manage pending changesets:

/changesets:list — overview of pending changesets with packages, bump types, and content previews
/changesets:update — modify an existing changeset's content or bump type
/changesets:merge — combine changesets that share the same bump type into a single file
/changesets:delete — remove a changeset that is no longer needed
/changesets:preview — preview the combined CHANGELOG output that the current set of changesets would produce