writing-changesets

Name: writing-changesets
Availability: InStock
Author: Hypercerts

Create ePDS changeset files with frontmatter and kebab-case names.

8|4|Updated Feb 20, 2026

Search Tags:#workflow #documentation #release-notes #changeset #audiences #ePDS

Ready to run

npx skills add https://github.com/hypercerts-org/ePDS --skill writing-changesets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-changesets
Source: https://github.com/hypercerts-org/ePDS/tree/main/.agents/skills/writing-changesets
Command: npx skills add https://github.com/hypercerts-org/ePDS --skill writing-changesets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams document user-facing or operator-facing changes to ePDS so downstream consumers can adapt without confusion.

Core Features & Use Cases

Create a changeset file in .changeset/ with a descriptive kebab-case name.
Provide frontmatter with the required 'ePDS' bump and a concise summary to guide release notes.
Align audiences and generate a single changelog entry for the root package during release.

Quick Start

Create a new changeset in .changeset/ with a descriptive kebab-case name and fill in the frontmatter to describe the change.

Frequently Asked Questions about writing-changesets

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

FAQPage Schema

How do I document ePDS release changes for downstream teams?▼

To document ePDS release changes, create a new changeset file under the .changeset directory using a descriptive kebab-case name, then add frontmatter with the required ePDS bump and a concise summary.

What is a changeset and when do I need one for ePDS releases?▼

A changeset is a machine-readable file that records user-facing or operator-facing modifications. You need one when documenting new features, config changes, or OAuth flow updates to ensure downstream consumers can adapt.

How do I write audience-aware release notes for config changes?▼

Writing audience-aware release notes involves adding a single summary to the changeset frontmatter and structuring the content to align with specific audiences, generating a single changelog entry for the root package during release.

Does this changeset workflow require a specific file naming convention?▼

Yes, the changeset workflow requires a new file placed under the .changeset directory with a descriptive kebab-case name to properly structure your ePDS release documentation.

What frontmatter is required in a changeset file for an ePDS bump?▼

The required frontmatter for a changeset file includes an ePDS bump declaration and a single concise summary to guide the generated release notes for downstream teams.