Index of every page on this site: llms.txt
All skills
pingdotgg avatar

/changesets

@b5453de
by Ping.ggpingdotgg/t3code67k stars
11,639
Run it yourself

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.

  • 2 files
  • 6.3 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/pingdotgg/t3code/changesets

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈58 tokens for metadata: the name and description. ≈873 when used: this file. ≈669 more on demand in 1 file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈231 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at b5453de. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago

README badge

README badge for pingdotgg/t3code/changesets