agentmods.dev

speckit-companion: Command for Claude Code

.claude/commands/changelog-entry.md

changelog-entry is a command for Claude Code from alfredoperez/speckit-companion. It costs 33 tokens per session (1,637 once invoked), scanned A, original, MIT.

A command for writing one changelog entry from a pull request or code diff. A changelog is a dated record of changes that users or developers may need to know about.

In plain words
What is it for?
Use it to inspect a pull request or branch diff and add an appropriate entry under the unreleased section of the correct changelog.
Why use it?
It avoids adding entries for internal changes users never see and applies the repository's required file, wording, and formatting rules.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

This is alfredoperez/speckit-companion's own configuration. It tells Claude Code how to work on speckit-companion itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything speckit-companion configures →

not rated 99repo changed 11d ago A scan 33 tokens original MIT
View source ↗ alfredoperez/speckit-companion speckit-companion.dev
Reuse

Borrowing it

Nothing to install: this file belongs to alfredoperez/speckit-companion. 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/alfredoperez/speckit-companion/main/.claude/commands/changelog-entry.md
Clone the repo
git clone --depth 1 https://github.com/alfredoperez/speckit-companion

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.

agentmods badge for changelog-entry

README.md
[![agentmods](https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/changelog-entry/github.svg)](https://agentmods.dev/commands/alfredoperez/speckit-companion/changelog-entry)
Your own site
<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/changelog-entry"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/changelog-entry/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.

agentmods 80×15 button for changelog-entry

Your own site · 80×15
<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/changelog-entry"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/changelog-entry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,637 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01637
Opus 5.5 $0.00013 $0.00655
Sonnet 5.5 $0.00007 $0.00327
Haiku 4.5 $0.00003 $0.00164

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

Security

Grade A, and why

changelog-entry 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 11d 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/changelog-entry.md · 62 lines

How it starts

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

Changelog entry

Write the entry for $ARGUMENTS (a PR number: gh pr view <N> and gh pr diff <N>), or for the current branch's diff against main when it is blank. The rules are "Changelog voice" at the end of this file; read them first, they are short.

  1. What does the user do or see? Say it in one sentence before writing anything. No entry, say so and stop, for: a change a user never meets (a refactor, a test, tooling, package size), a docs or site change, a change to the wording of the Companion's own prompts, and a fix to something added in this same unreleased block (edit that entry instead).
  2. Fold before you add. Read the [Unreleased] block first. When it already has an entry for the same area and the same kind of change, rewrite that entry to cover both and add this PR's link to it. Small UI polish (wrapping, spacing, an empty state, a tab title) is always one line per area, never a line per fix. A release holds at most 12 bullets and 3 highlights, and the test fails past that.
  3. Which file. By where the change lives, one entry per file it touches:
    • apps/speckit-extension/ → apps/speckit-extension/CHANGELOG.md
    • apps/claude-mod/ → apps/claude-mod/CHANGELOG.md (no PR link, no area tag, no ==)
    • apps/copilot-canvas/ → apps/copilot-canvas/CHANGELOG.md (no PR link, no area tag)
    • the VS Code extension → root CHANGELOG.md
  4. Bullet or highlight. A highlight is a feature worth a picture; everything else is a bullet under Added, Changed, Fixed or Security.
  5. Write it under ## [Unreleased], never under a version, and leave every version number alone.
    • Bullet: - **Title of at most 8 words.** One sentence of at most 22 words. ([#N](https://github.com/alfredoperez/speckit-companion/pull/N)) <!-- area: <id> -->
    • Highlight: a #### Title, at most two such sentences, then <!-- area: <id>; pr: N; media: <ids> -->
    • Second person, present tense, what you do or see first. At most one ==phrase== of two to four words. Setting keys, commands and button names in code or bold. No file or symbol names, no "now", no "previously", no history of the bug.
  6. Area. One id from apps/website/src/components/changelog/changelogAreas.ts.
  7. Picture. For a highlight, look for a matching shot in tooling/scripts/shots.json (its output is .shots/) and name its id under media:; a media id also needs its entry in content/media/changelog.json or the site build fails. No shot fits: say which one is missing instead of inventing an id.
  8. Check. npm test -- docs-consistency names any entry that breaks a rule. Cut words until it passes; a fact that does not fit belongs in the docs page.

Report the entry as written and the file it went into.

Read the full file on GitHub · 62 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.

  1. 11d ago Changed · +36 lines c320211e5090
  2. 19d ago First seen · 26 lines · 33 tokens per session scan A 46f59ea962d9

Subscribe to this mod's changes

changelog-entry is a command published in the GitHub repository alfredoperez/speckit-companion (99 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 1,637 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-10-06.

Claude CodeCommitsGit and workflowTypeScriptWriting and docsai-toolsdeveloper-toolsspec-driven-developmentvscode-extension
Related

Other commands, from other repositories

commit

When you receive this command, do the following.

lucasrosati/claude-code-memory-setup · 0 tokens

pre-commit-check

Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.

TheBeardedBearSAS/claude-craft · 6 tokens

pre-commit-audit

Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers. Use when the user requests a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode…

flonat/flonat-research · 94 tokens

commit

Stage and commit with a conventional-commit message the auto-release bot can read.

DailybotHQ/deepworkplan-skill · 15 tokens

branch-commit

Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…

Mozurok/fhorja.dev · 111 tokens

approve-proposed

Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block, promoting staged content to real files. Invoked on request only. Use when that block contained files marked PROPOSED and you have accepted the inline content of each. Do not use when the prior turn had…

Mozurok/fhorja.dev · 107 tokens