changesets skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
changesets is agent-read markdown (skill) from deathemperor/infinitus: Changesets. Use after consumer-visible runtime, public API, entrypoint, lifecycle, or wire-format changes, when deciding whether a change is breaking, or when authoring changesets and consumer release notes..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
Record what consumers need to know after implementation and focused validation. ## Workflow 1. Inspect the complete diff 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 either a reason no changeset is required or one coherent changeset. When required, read [authoring.md](authoring.md). 5. Validate package names, frontmatter, bump policy, and consumer-facing text. Do not include unrelated worktree changes. ## 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 …
Read the whole file at its exact version.
How to install
mdr add deathemperor/infinitus/changesets@git:20260918.e3c85eamdr add deathemperor/infinitus/changesets@sha256:285aa88c9322edf4Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ynfgq5row2xmpyyb)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2854 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
deathemperor/infinitus · 6 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ynfgq5row2xmpyyb GET https://markdownregistry.com/api/v1/resolve?ref=deathemperor/infinitus/changesets GET https://markdownregistry.com/api/v1/blob/285aa88c9322edf4f91f556e03dcf96863aff7fdb18aae48461b65bc6f6f42e5
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from deathemperor/infinitus
Every file in deathemperor/infinitus