A release-quality check for SpecKit Companion that examines the changes since the last version tag, runs automated checks, performs selected desktop checks, and writes one report.

It helps run release-wide checks, repeat failed or blocked checks after fixes, and create a dated quality report that publishing commands can require.

It focuses testing on what changed in the release and provides a ship-or-fix-first decision before publishing.

How alfredoperez/speckit-companion configures Claude Code

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/release-qa.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/release-qa/github.svg)](https://agentmods.dev/commands/alfredoperez/speckit-companion/release-qa)

Your own site

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

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

When invoked 831 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.00060	$0.00831
Opus 5.5	$0.00024	$0.00332
Sonnet 5.5	$0.00012	$0.00166
Haiku 4.5	$0.00006	$0.00083

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

Security

Grade A, and why

release-qa 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 16d 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/release-qa.md · 39 lines

How it starts

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

What this does

QA for a release, once, at the end of a batch. It is issue-agnostic: it reads what is being released (the diff since the last v* tag and the ## [Unreleased] sections of both changelogs), not a ticket list. It is step 3 of /release-loop (and recheck is step 6); every /publish* command refuses to tag without its report.

Run

Load the release-qa skill and follow it in order: Step 0 scope, Step 1 automated gates, Step 2 scripted and desktop checks, Step 3 report. The skill owns the flow, .claude/skills/release-qa/surface-map.yml owns which paths need which checks, and the helper scripts next to it do the mechanical work.

$ARGUMENTS:

empty: the full run, baseline included.
recheck: after fixes. Repeats the automated gates and only the checks that ended FAIL or BLOCKED in the latest report, and writes a new report against the new HEAD.

The result is one note, Projects/speckit companion/QA Report <YYYY-MM-DD>.md in the vault. Raw evidence stays in the sibling speckit-sandboxes checkout, under $EVIDENCE_DIR/<date>-release-qa/ (and $EVIDENCE_DIR/<date>-qa-<name>/ for what qa-stage.sh stages); . .claude/sandboxes-env.sh sets $EVIDENCE_DIR.

Release gate

The publish commands run this before they tag. The gate passes only when all three hold:

The newest Projects/speckit companion/QA Report*.md in ~/dev/GitHub/obsidian-vault exists.
Its head frontmatter equals git rev-parse --short HEAD, or every commit in git log <head>..HEAD --format=%s is a release commit (chore: bump version to …, or chore(speckit-ext): release …, chore(claude-mod): release … or chore(canvas): release …). Anything else means the report is for other code.
It says verdict: ship and fails: 0.

When it does not pass, stop and say why in one line: no report, a report for another sha (name both), or the open FAIL checks. The fix is /release-qa (or /release-qa recheck after fixes).

Only an explicit instruction in the conversation to skip QA for this release overrides the gate. Say QA gate overridden in the release report.

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

16d ago Changed dd5506c62711
19d ago Changed 0f8c8a5a677c
21d ago Changed 3774ec6074a6
23d ago First seen · 39 lines · 60 tokens per session scan A 6a6edea96585

Subscribe to this mod's changes

release-qa is a command published in the GitHub repository alfredoperez/speckit-companion (99 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 831 once invoked, about $0.0002 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-02.

Claude Code Git and workflow Releases Testing TypeScript ai-tools developer-tools spec-driven-development vscode-extension

speckit-companion: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

What this does

Run

Release gate

What this file has done since we first saw it

Other commands, from other repositories

pr-ready

ship

4-close-project

release-check

repo-sprint

run-release