Agent skill

Changesets

by foldkit in foldkit/foldkit

Concise PR finalization changesets. An agent skill from foldkit/foldkit.

MITAuto-check passedDevelopment

Install Changesets

skills CLI
$ npx skills add foldkit/foldkit --skill changesets -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install foldkit/foldkit changesets --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/foldkit/foldkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/repos/effect/.agents/skills/changesets .claude/skills/changesets && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
changesets
GitHub stars
912
Token cost
~923 tokens
SKILL.md length
454 words
Files
2
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Concise PR finalization changesets. An agent skill from foldkit/foldkit.

  • Works in 5 steps: Inspect the complete diff from the merge… → Classify impact across source types,… → Perform the breaking audit below. → …
  • Implementation scope is complete and focused validation has finished to classify release impact
  • SKILL.md covers Workflow, PR-level consolidation, Requirement and Breaking Audit
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Changesets is an agent skill from foldkit/foldkit. Concise PR finalization changesets. Use when implementation scope is complete and focused validation has finished to classify release impact, consolidate the PR's existing changeset, or write its consumer release note.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `authoring.md`).

It sits in Development, covering Changelog and release notes. The licence is MIT.

When your agent uses it

  • Implementation scope is complete and focused validation has finished to classify release impact
  • Consolidate the PRs existing changeset
  • Write its consumer release note

Example prompts

  • “/changesets”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the complete diff from the merge base, including changeset files
  2. Classify impact across source types, runtime behavior, entrypoints, required
  3. Perform the breaking audit below.
  4. Record a reason no changeset is required, or update the PR's existing
  5. Validate package names, frontmatter, bump policy, and a concise

What it can do on your machine

Read from SKILL.md and the folder at commit ffbbde1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Changesets loads about 923 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 454 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~923

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from foldkit/foldkit at commit ffbbde1, republished under its MIT licence (© foldkit). 454 words, ~923 tokens.

Download SKILL.mdSave it as .claude/skills/changesets/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
changesets
description
Concise PR finalization changesets. Use when implementation scope is complete and focused validation has finished to classify release impact, consolidate the PR's existing changeset, or write its consumer release note.

Treat a changeset as the release note for the complete PR, not as a log of work performed along the way. Finalize it after the current implementation scope and focused validation are complete.

Workflow

  1. Inspect the complete diff from the merge base, including changeset files already introduced by the PR, and identify directly affected published packages.
  2. Classify impact across source types, runtime behavior, entrypoints, required services, lifecycle, and persisted or wire data.
  3. Perform the breaking audit below.
  4. Record a reason no changeset is required, or update the PR's existing changeset. Create one only when the PR does not have one. When required, read authoring.md.
  5. Validate package names, frontmatter, bump policy, and a concise consumer-facing description.

Do not include unrelated worktree changes.

PR-level consolidation

The default is one changeset file per PR. One file can name several packages and summarize several related fixes or additions. Successive prompts, commits, and subtasks within the same PR update that file. If implementation resumes after a changeset was drafted, revise it during the next finalization pass.

Use separate files only when a maintainer requests the split or the PR contains independent changes that need separate release notes.

Requirement

Create a changeset for observable runtime behavior changes, including bug fixes; exported value or public type changes; entrypoint or export-map changes; changes to required services, errors, ownership, defaults, or lifecycle; and persisted, serialization, protocol, or wire-format changes.

Tests-only changes, behavior-preserving internal refactors, documentation or JSDoc maintenance, and unpublished tooling normally do not need one. When unclear, inspect exports and consumer-visible declarations rather than inferring from source location.

Show full SKILL.md (189 more words)Show less

Breaking Audit

A change is breaking when valid existing consumer code, configuration, or data must change to keep compiling or behaving according to the previous contract. Audit every surface:

  • Names and locations: exports, entrypoints, compatibility exports, and module paths.
  • Call compatibility: parameters, accepted inputs, overload resolution, generic parameters, and defaults.
  • Result compatibility: return and error types, output narrowing, members, inference, and required services.
  • Runtime contracts: defaults, failures, interruption, concurrency, ordering, resource lifetime, acquisition, cleanup, and mutation.
  • Data compatibility: persisted schemas, encodings, database layouts, protocols, and wire formats.

Additive exports, optional parameters, and behavior-preserving implementations are normally non-breaking. A fix restoring the documented contract is normally non-breaking but still needs a changeset when its operational impact is consumer-visible. Verify representative existing calls when overload ordering, structural assignability, or inference makes compatibility uncertain. API diff output is mechanical evidence, not a semantic-version decision.

The task is complete when every affected contract and published package is accounted for and either the no-changeset decision is explicit or the PR has one consolidated, valid changeset by default. Its release note describes the consumer impact and migration for every break without repeating the PR description.

© foldkit, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in repos/effect/.agents/skills/changesets of foldkit/foldkit.

  • SKILL.md
  • authoring.md

Open the folder on GitHubat commit ffbbde1

Compare with similar skills

Changesets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Changesets compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changesets this skillfoldkit/foldkit912—~923Automated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
StarRocks Release NotesStarRocks/starrocks12k—~1.9kAutomated safety check: NotesApache-2.0
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Mole CLI Release Flowtw93/Mole69k—~2.5kAutomated safety check: PassGPL-3.0

Similar skills

  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed
  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes
  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed
  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    69k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

More from foldkit/foldkit

All 17 skills in this repo
  • Commit Changes

    foldkit/foldkit

    Create a git commit in the Foldkit monorepo with changeset enforcement and formatting.

    912 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Foldkit

    foldkit/foldkit

    A skill your agent uses whenever working with Foldkit. An agent skill from foldkit/foldkit.

    912 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Audit Program

    foldkit/foldkit

    Audit an existing Foldkit program against the architecture, conventions, and quality bar.

    912 GitHub stars~7.2k tokensUpdated today
    Auto-check passed
  • Generate Program

    foldkit/foldkit

    Generate a complete, idiomatic Foldkit program from a natural language description.

    912 GitHub stars~20k tokensUpdated today
    Auto-check passed
  • Dependency Maintenance

    foldkit/foldkit

    Dependency maintenance. An agent skill from foldkit/foldkit.

    912 GitHub stars~683 tokensUpdated today
    Auto-check passed
  • Review Contributor PR

    foldkit/foldkit

    Review, discuss, or finish a Foldkit pull request opened by an external contributor.

    912 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Changesets

What does Changesets do?

Concise PR finalization changesets. An agent skill from foldkit/foldkit. Changesets is an agent skill from foldkit/foldkit. Concise PR finalization changesets.

When should I use Changesets?

Changesets fits situations like: implementation scope is complete and focused validation has finished to classify release impact; consolidate the PRs existing changeset; write its consumer release note.

How do I install Changesets in Claude Code?

Run `npx skills add foldkit/foldkit --skill changesets -a claude-code`. Or copy the skill folder (repos/effect/.agents/skills/changesets in foldkit/foldkit) into .claude/skills/changesets in your project. Claude Code loads it when a task matches its description.

How do I install Changesets in Codex?

Run `npx skills add foldkit/foldkit --skill changesets -a codex`. Or copy the skill folder (repos/effect/.agents/skills/changesets in foldkit/foldkit) into .agents/skills/changesets in your project. Codex loads it when a task matches its description.

Can I use Changesets in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add foldkit/foldkit --skill changesets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changesets, .gemini/skills/changesets, .github/skills/changesets and .opencode/skills/changesets in your project.

What does Changesets need to run?

SKILL.md names no scripts, command-line tools or credentials: Changesets is instructions for the agent only.

Does Changesets access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Changesets safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Changesets use?

Changesets is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Changesets use?

About 923 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Changesets?

Skills that share tags, products or a category with Changesets: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changesets?

foldkit (a GitHub organization) maintains it in foldkit/foldkit, which has 912 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: foldkit/foldkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.