changesets-hygiene

Enforce .changeset entries and prevent manual version or changelog edits.

1|Updated Jul 7, 2022
One-click install
npx skills add https://github.com/chiubaka/circleci-orb --skill changesets-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changesets-hygiene
Source: https://github.com/chiubaka/circleci-orb/tree/main/org/agents/skills/changesets-hygiene
Command: npx skills add https://github.com/chiubaka/circleci-orb --skill changesets-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that version bumps and consumer-facing CHANGELOG entries in Changesets-driven repositories are sourced from Changesets, not from manual edits to package.json and CHANGELOG.md.

Core Features & Use Cases

  • Prevent Manual Edits: Avoids the synchronization issues and duplication of entries that arise from manual version or changelog edits.
  • Changesets Integration: Facilitates the use of .changeset entries and changeset add/version flows for accurate release tracking.
  • Guidance for PRs: Offers clear guidelines on when to add a Changeset, ensuring only relevant changes are recorded.

Quick Start

Ensure release integrity by adding a .changeset file when bumping versions in a Changesets-driven repository.

Frequently Asked Questions about changesets-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent manual edits to package.json and CHANGELOG.md in a Changesets repository?

Prevent manual edits by enforcing .changeset entries for version bumps and changelog updates. This avoids synchronization issues and duplicated entries, ensuring all release tracking is sourced from the Changesets flow.

When do I need to add a Changeset entry to my pull request?

Add a Changeset entry when your pull request introduces changes that warrant a version bump or consumer-facing changelog update. Clear guidelines help ensure only relevant changes are recorded in the release tracking process.

Does this work with any repository using @changesets/cli?

Yes, it applies to any repository configured with a .changeset/config.json file and the @changesets/cli package. It integrates with the changeset add and version flows to maintain automated release tracking and versioning integrity.

Why does manually updating the version in package.json cause release issues?

Manual version updates cause synchronization issues and duplicate changelog entries because they bypass the automated Changesets flow. Relying on .changeset entries ensures accurate, conflict-free release tracking across the repository.

What is the best way to manage version bumps in a Changesets-driven monorepo?

The best way is using the changeset add and version flows to generate .changeset entries, which automatically synchronize package.json versions and CHANGELOG.md files without requiring manual edits or risking duplication.