More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Token release review

    2

    Catch breaking token changes before you publish, get the right semver bump and a ready changelog section.

    Free

    Security scanned
    Token release review

    Token release review

    Example session with this skill installed

    We're about to release our tokens as 1.5.0. Can you check what changed since 1.4.0
    and write the changelog? The tokens are in tokens/, and 1.4.0 is checked out in
    ../tokens-1.4.0.

    • Read your context and instructions
    • Compiled the token release review

    Stop before releasing 1.5.0: this release needs a major. It removes one token and renames another, and code that uses them stops working after the upgrade. Publishing it as a minor would break everyone on ^1.4.0.

    VerdictBreaking release, suggested version major
    Planned1.5.0 (minor)
    Changes1 removed · 1 renamed · 6 changed (+3 through references) · 2 added

    Two ways out: release

    2.0.0, or keep space-sm and color-danger as deprecated aliases in 1.5.0 and remove them in 2.0.0.

    Decisions for you

    1. color-danger was removed, and color-critical was added with the same value (#ef4444). This looks like a rename dsgraph could not match by name. If it is one, I'll declare it in dsgraph.config.json ("renames": { "color-danger": "color-critical" }), and the changelog will tell consumers what to replace.
    2. space-sm → space-small is a guess (59%) from the same value and a similar name. Please confirm.

    color-accent changed in the dark theme only (#60a5fa → #7aa2ff, another hue, noticeable). Is that intended? The light theme changes through color-blue-500.

    Changelog section (draft in CHANGELOG.md, waiting for your answers):

    
## 2.0.0

### Breaking
- `color-danger` is removed. Use `color-critical` (same value, #ef4444).
- `space-sm` is renamed to `space-small`. Replace the old name.

### Looks different
- `color-blue-500`: #2563eb → #3366ff, lighter, noticeable (ΔE 3.36); also changes `color-accent`.
- `color-gray-900`: #111827 → #0b0f19, darker, noticeable (ΔE 4.17); also changes `color-bg` and `color-text`.
- `color-accent` (dark theme): #60a5fa → #7aa2ff, another hue (ΔE 2.84).
- `radius-md`: 6px → 8px.
- `space-lg`: 24px → 28px.
- `shadow-card`: blur and color changed.

### New
- `color-critical` (#ef4444)
- `duration-slow` (320ms)

    Next steps: answer the three questions, pick 2.0.0 or the alias route, and I'll finalise the changelog. The full report is in release-report.md. To catch this on every pull request, the same check runs in CI with the dsgraph GitHub Action (fail-on: major).

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A JSON diff hides what hurts the people who use your design system. A rename looks like a removal plus an addition. A changed base color silently changes every token that refers to it. A value can change in the dark theme only. And the version number is a guess, so a removal ships as a minor and breaks everyone who upgrades.

    This skill reviews a token release the way a consumer experiences it. Your agent compares the release with the last published version using dsgraph, an open-source engine that resolves every reference in every theme, matches tokens across versions and judges each change by its effect. Then it does the parts that need judgment:

    • Checks the version number. If the release removes or renames tokens but is planned as a minor, it stops and tells you before anything else, with the two ways out: release a major, or keep the old names as deprecated aliases.
    • Puts the doubtful calls in front of you. Renames dsgraph is not sure about, removals that look like renames, changes in one theme only. It does not decide these on its own.
    • Writes the changelog section grouped by impact, with what to use instead of every removed token, and never invents a reason or a replacement.

    What you get: the verdict and the bump the release needs, a short list of decisions, and a changelog section in your project's format.

    Reads: DTCG 2025.10 (resolver documents and modes included), older token JSON with value and type, CSS custom properties with themes. From a folder, an npm package or a GitHub repository.

    Runs locally. The checks run through npx @dsgraph/cli; nothing is uploaded. Free and open source (MIT).

    • Renames are inferred from the same value in every theme and a similar name. A rename to a very different name shows as a removal plus an addition until it is declared in dsgraph.config.json; the skill points these out.
    • It compares one source of truth per side. If a package ships several builds of the same tokens (CSS and JSON), it compares one of them.
    • Token formats outside DTCG, token JSON and CSS custom properties (SCSS maps, JS objects) are not read as tokens.
    • The changelog's "why" comes from you or the pull request; the skill does not invent reasons.

    Open docs

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 16 days ago

    • Free with an Agensi account

    Accounts
    GitHub
    Software
    Node.jsGit@dsgraph/cli

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Environment Variables

    Allowed Hosts

    registry.npmjs.org
    cdn.jsdelivr.net
    github.com

    File Scopes

    tokens/**
    **/*.tokens.json
    **/*.resolver.json
    CHANGELOG.md
    .changeset/**
    dsgraph.config.json
    release-report.md

    Network access downloads the dsgraph CLI from npm and, when a version is given as a package or repository, its token files from jsDelivr or GitHub. `GITHUB_TOKEN` is read only to fetch a private repository the user names, and only by dsgraph, sent to GitHub. Files written: the report, the changelog draft and, when the user confirms a rename, `dsgraph.config.json`. The skill never edits tokens, never changes the version number and never publishes.

    Listed16 days ago

    What's inside

    Frequently Asked Questions

    No. dsgraph is an open-source CLI that runs on your machine. A GitHub token is needed only to read a private repository.

    The last published one: the npm package, the last release tag on GitHub, or a folder checked out from that tag. If it can't tell, it asks.

    No. It tells you the bump the release needs and drafts the changelog; you make the release.

    The same comparison runs in CI with the dsgraph GitHub Action (`specsure/dsgraph-action@v1`). The skill mentions it but doesn't add it unless you ask.

    New in Frontend & Web Apps

    Free