What is zag-changelog?

A command that copies relevant new changes from the Zag repository into Ark UI framework changelogs. A changelog is a record of software changes between releases.

It is for finding unreleased Zag changes, reviewing which ones should be included, and creating an Ark UI changeset after confirmation.

It helps keep Ark UI's release notes aligned with changes in the underlying Zag project while filtering out changes that do not affect Ark UI.

How chakra-ui/ark configures Claude Code

About the project

Ark UI is a headless component library: it supplies accessible UI behavior and structure without visual styling, so developers can build their own design systems. It supports React, Vue, Solid, and Svelte applications.

chakra-ui/ark · 5,453 stars · on GitHub · ark-ui.com

Reuse

Borrowing it

Nothing to install: this file belongs to chakra-ui/ark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/chakra-ui/ark/main/.claude/commands/zag-changelog.md

Clone the repo

git clone --depth 1 https://github.com/chakra-ui/ark

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/chakra-ui/ark/zag-changelog/github.svg)](https://agentmods.dev/commands/chakra-ui/ark/zag-changelog)

Your own site

<a href="https://agentmods.dev/commands/chakra-ui/ark/zag-changelog"><img src="https://agentmods.dev/badge/commands/chakra-ui/ark/zag-changelog/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/chakra-ui/ark/zag-changelog"><img src="https://agentmods.dev/badge/commands/chakra-ui/ark/zag-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 962 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.00962
Opus 5.5	$0.00007	$0.00385
Sonnet 5.5	$0.00004	$0.00192
Haiku 4.5	$0.00002	$0.00096

Measured 2mo ago against content hash da32923978c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zag-changelog scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/zag-changelog.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Steps

Fetch the latest CHANGELOG.md from the chakra-ui/zag repository
- Use gh api repos/chakra-ui/zag/contents/CHANGELOG.md -H "Accept: application/vnd.github.raw+json" to get the changelog content
Determine which Zag versions are new
- Check the current @zag-js/* version in packages/react/package.json
- Compare the latest Ark UI release changelog (packages/react/CHANGELOG.md) against the Zag changelog
- Identify Zag versions whose changes are NOT yet reflected in the Ark UI changelogs
Parse the new changes from Zag.js changelog
- Extract all entries from the new Zag versions
- Identify component-specific changes and general improvements
- Filter out Zag.js internal changes that don't affect Ark UI (build system, core state machine internals, docs-only, framework-specific fixes for frameworks Ark doesn't use like Preact/Vanilla)
Review the changes with me before applying
- Show me the extracted changes
- Confirm which changes should be synced to Ark UI
- Ask if any changes need framework-specific notes
Create a changeset file in .changeset/
- Use the format from existing changesets (YAML frontmatter with package names and bump type)
- Include all four frameworks: @ark-ui/react, @ark-ui/solid, @ark-ui/svelte, @ark-ui/vue
- Use patch for bug fixes, minor for new features
- Do NOT modify the CHANGELOG.md files directly
Show me a summary of all changes made
- List which components were updated
- Highlight any differences between frameworks (if applicable)

Important Notes

Only sync changes that are relevant to Ark UI components
Skip Zag.js internal changes (build system, documentation-only, core machine internals, etc.)
Create changesets (.changeset/*.md) instead of editing CHANGELOG.md files directly

Writing Style

Follow the tone guide in TONE_OF_VOICE.md. Changelogs are user-facing — write them like you're telling a developer what's new, not filing a spec.

Read the full file on GitHub · 101 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 101 lines · 18 tokens per session scan A da32923978c0

Subscribe to this mod's changes

zag-changelog is a command published in the GitHub repository chakra-ui/ark (5,453 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 962 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Frontend Git and workflow React components design-system headless solid vue

zag-changelog next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
zag-changelogchakra-ui/ark	Command	5.5k	2d ago	MIT	A	18	Claude Code
barista-fixfrappe/frappe-ui	Command	1.1k	2d ago	MIT	A	17	Claude Code
implement-featureHoangNguyen0403/agent-skills-standard	Command	583	today	MIT	A	0	Claude Code
gen-videoAdityaraj0421/naksha-studio	Command	353	19d ago	MIT	A	56	Claude Code
releasejezweb/claude-skills	Command	1.1k	28d ago	MIT	B	7	Claude Code
prepare-releasesaeedkolivand/ai-job-hunter-app	Command	63	yesterday	Apache-2.0	A	20	Claude Code
initmahmoudilyan/marmoui	Command	20	3mo ago	MIT	A	39	Claude Code

ark: Command for Claude Code