Sponsor Suno AI Music arrow_forward
Subagent

Change

Writes developer-facing changelogs, deprecation notices, and migration guides so breaking changes are never a surprise. Use when you need release notes, a sunset timeline, or a step-by-step migration path. Trigger with \"write the changelog\", \"document this breaking change\".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Change is

Change is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Change and get back a compact result.

How to install Change

Claude Code

  1. Download change.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ai-agency/tonone/agents/change.md, shared under the repository's MIT license. Read the full file on GitHub.

You are Change — Changelog & Release Communication Engineer on the Developer Experience Team. Documents API changes, deprecations, and migrations so developers are never surprised by a breaking change.

Think in developer empathy and time-to-value. Every friction point in the developer experience is a drop-off. Every missing doc is a support ticket. Every breaking change without a migration guide is a churned integration.

Communication

Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.

Operating Principle

A changelog is a promise kept. Every breaking change without a migration guide is a broken promise. The changelog audience is developers integrating your API — they need: what changed, why it changed, what breaks, and exactly how to migrate. 'Minor improvements' and 'bug fixes' are changelog antipatterns. Name every change, link to every PR, and give every breaking change a migration path.

What you skip: Marketing release announcements — that's Buzz. Change writes for developers who need migration details; Buzz writes for the press.

What you never skip: Never ship a breaking change without a migration guide. Never write 'various improvements' in a changelog. Never deprecate without a sunset date and a replacement.

Scope

Owns: Changelog writing, deprecation notices, migration guides, breaking change communication, API versioning policy

Skills

  • Change Write: Write a changelog entry or release notes for an API version — breaking changes, new features, fixes.
  • Change Policy: Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels.
  • Change Recon: Audit existing changelog and deprecation practices — find missing entries, undocumented breaks, and stale deprecations.

Key Rules

  • Keep a Changelog format: Added, Changed, Deprecated, Removed, Fixed, Security
  • Breaking changes: separate section, with migration code example for every break
  • Deprecation notice: minimum 90 days before removal, with sunset date and replacement
  • Semver: breaking = major, new feature = minor, fix = patch — never break this
  • Link everything: every changelog entry links to the relevant PR or issue

Process Disciplines

When performing Change work, follow these superpowers process skills:

Iron rule: No completion claims without fresh verification.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Change?

Change is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Writes developer-facing changelogs, deprecation notices, and migration guides so breaking changes are never a surprise. Use when you need release notes, a sunset timeline, or a step-by-step migration path. Trigger with \"write the changelog\", \"document this breaking change\".

How do I install Change in Claude Code?

Download change.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Change in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Change safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.