Api changelog

Skill shinzoxD/knackbox/skills/coding/api-changelog

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install

npx -y skills add shinzoxD/knackbox --skill api-changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write consumer-facing API changelogs and migration notes for breaking and additive changes. Use whenever the user asks for an API changelog, OpenAPI migration notes, deprecation announcement, version diff summary, or how to communicate a breaking API change to clients.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.5 KB, as published. Nobody here has run it

API Changelog

API consumers need precise deltas: what changed, who is affected, and how to migrate. Prefer machine-readable intent plus human migration steps.

Sections

# API changelog — <service> <version or date>

## Summary
One paragraph.

## Breaking changes
- …

## Deprecations
- … (removal date if known)

## Additive changes
- …

## Bug fixes (API-visible)
- …

## Migration guide
### Before
### After
### Rollout / dual-run

## OpenAPI / SDK notes
…

Rules

Never invent endpoints or fields not in the source material.
Label breaking vs non-breaking carefully (nullability, enum, auth).
Include example requests/responses for migrations.
Deprecations need timeline and replacement.
Separate internal refactors that do not affect clients.
Link ticket/RFC ids when provided.

Edge cases

GraphQL: field deprecation directives and client query impact.
Webhooks: payload changes and signature versioning.
Errors: new codes clients must handle.