What is speckit.changelog?

A command that creates Rush change entries for the VChart monorepo from the project’s feature specification and plan. A monorepo is one repository containing multiple related packages; a Rush change entry records the release impact of a package change.

Finding the matching feature spec, summarizing its planned change, and choosing a release bump type when generating a Rush change entry.

It avoids asking for information that can already be inferred from the branch and specification. Using the plan as the source keeps the release note tied to the intended feature.

How VisActor/VChart configures Claude Code and Cursor

About the project

VChart is a cross-platform charting library for building data visualizations and annotated, animated storytelling charts. Developers use it across desktop, mobile web, and several mini-program environments through its core and framework-specific packages. The catalogue entries support work with this charting project.

VisActor/VChart · 1,855 stars · on GitHub · visactor.io

Reuse

Borrowing it

Nothing to install: this file belongs to VisActor/VChart. 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/VisActor/VChart/develop/.cursor/commands/speckit.changelog.md

Clone the repo

git clone --depth 1 https://github.com/VisActor/VChart

Made for: Claude Code, Cursor.

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/visactor/vchart/speckit.changelog/github.svg)](https://agentmods.dev/commands/visactor/vchart/speckit.changelog)

Your own site

<a href="https://agentmods.dev/commands/visactor/vchart/speckit.changelog"><img src="https://agentmods.dev/badge/commands/visactor/vchart/speckit.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/visactor/vchart/speckit.changelog"><img src="https://agentmods.dev/badge/commands/visactor/vchart/speckit.changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 872 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.00035	$0.00872
Opus 5.5	$0.00014	$0.00349
Sonnet 5.5	$0.00007	$0.00174
Haiku 4.5	$0.00003	$0.00087

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

Security

Grade A, and why

speckit.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.

.cursor/commands/speckit.changelog.md · 64 lines

How it starts

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

User Input

$ARGUMENTS

Outline

Resolve feature spec from branch:
- Treat this command as zero/low-input: if $ARGUMENTS is empty, infer everything from the current branch and specs directory.
- Derive the feature prefix from the current branch name (for example, 001-fix-bug → prefix 001) and locate the matching directory under specs/ whose name starts with that prefix.
- From that directory, resolve:
  - plan.md as the primary source of truth for the change description.
  - checklists/requirements.md as an optional, secondary source when the plan lacks a clear summary.
- If no matching specs/<spec-id>/ can be found, return an error instead of guessing.
Extract Summary from specs-only context:
- From plan.md, read the ## Summary section and take the first non-empty line as the feature summary.
- If the Summary section is empty or missing, fall back in order to:
  - The top-level title of plan.md (for example, Implementation Plan: ...).
  - A concise line derived from checklists/requirements.md.
  - The feature directory name or branch name.
- Normalize the final summary to a single line (strip markdown markers, collapse whitespace) without inventing new wording.
Infer bump type (spec-driven):
- Default bumpType to patch.
- Scan the content of plan.md (case-insensitive) for explicit markers:
  - If it contains BREAKING CHANGE or a clear MAJOR marker → use major.
  - Else if it contains a clear MINOR marker → use minor.
  - Else if it only contains PATCH or no marker at all → keep patch.
- If the user passes an explicit bump type argument, validate it against patch | minor | major | none and override the inferred value. none means "no version bump" while still allowing a change file to be written if Rush supports it.
Construct the Rush change message (no git history):
- Build a single-line message using the spec id and the inferred summary, for example:
  - update changes for <spec-id>: <summary sentence>
- If the user provided an explicit message argument, prefer that over the inferred one.
- Do not analyze git commit history, file diffs, or common/changes contents when constructing this message; the only semantic source is specs/<spec-id>/.

Read the full file on GitHub · 64 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 · 64 lines · 35 tokens per session scan A 0e59a2b2816d

Subscribe to this mod's changes

speckit.changelog is a command published in the GitHub repository VisActor/VChart (1,855 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 872 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.

3dchart Git and workflow Releases canvas canvas2d chart charting-library datavisualization

speckit.changelog next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
speckit.changelogVisActor/VChart	Command	1.9k	yesterday	MIT	A	35	Claude Code, Cursor
landgmickel/flow-next	Command	717	yesterday	MIT	A	13	Claude Code
qualityDesko77/claude-code-skills-1c	Command	90	yesterday	MIT	A	18	Claude Code
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
release-managerruvnet/agentic-flow	Command	838	today	none	A	0	Claude Code
create-prdsswift/ion	Command	5	yesterday	MIT	A	28	Claude Code
rally-merge-prddgonzal3/rally	Command	6	3d ago	MIT	A	0	Claude Code

VChart: Command for Claude Code