---
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.
title: changesets
canonical_url: https://skilld.dev/gh/pingdotgg/t3code/changesets
last_updated: 2026-11-12T14:20:12.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [authoring.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/changesets/authoring.md).
>
> If the user asked to install this Skill, run `npx skilld install pingdotgg/t3code/changesets`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/changesets`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/pingdotgg/t3code/changesets) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/changesets`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/changesets --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/changesets --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

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](https://skilld.dev/api/skills-raw/pingdotgg/t3code/changesets/authoring.md).
5. Validate package names, frontmatter, bump policy, and a one-sentence
   consumer-facing description, longer only for breaks or required migration.

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.

## 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 is one sentence of
consumer impact, plus migration steps for every break, with no implementation
detail.
