What is release-check?

A pre-release command checklist for markupr, covering its desktop app, command-line tool, and MCP server.

Checking release readiness, reviewing recent commits, confirming package versions, and producing a summary before publishing a new version.

It catches failed tests, build or type errors, version mismatches, native dependency problems, and uncommitted changes before a release is made.

How eddiesanjuan/markupr configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to eddiesanjuan/markupr. 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/eddiesanjuan/markupr/main/.claude/commands/release-check.md

Clone the repo

git clone --depth 1 https://github.com/eddiesanjuan/markupr

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/eddiesanjuan/markupr/release-check.svg)](https://agentmods.dev/commands/eddiesanjuan/markupr/release-check)

Your own site

<a href="https://agentmods.dev/commands/eddiesanjuan/markupr/release-check"><img src="https://agentmods.dev/badge/commands/eddiesanjuan/markupr/release-check.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 379 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.00000	$0.00379
Opus 5	$0.00000	$0.00189
Sonnet 5	$0.00000	$0.00076
Haiku 4.5	$0.00000	$0.00038

Measured 8d ago against content hash 0a11e9694b5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

release-check 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 8d 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-check.md · 55 lines

What it actually says

Pre-Release Checklist

Validate that markupr is ready for a new release. Run this before bumping the version.

Instructions

Verify the build succeeds:
```
npm run build
```
This builds the desktop app, CLI, and MCP server. All three must succeed.
Run the full test suite:
```
npm test -- --run
```
All tests must pass. Do not proceed if any fail.
Run lint and type checking:
```
npm run lint
npm run typecheck
```
Zero errors required. Warnings are acceptable but should be noted.
Check version consistency:
- Read package.json for the current version
- Read CLAUDE.md for the documented version
- Read electron-builder.yml for the builder config version
- Flag any mismatches
Review recent changes since last release:
```
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~20)..HEAD
```
Categorize commits as: features, fixes, chores, breaking changes.
Check for uncommitted changes:
```
git status
```
Working tree should be clean before release.
Verify native dependencies:
```
npm ls keytar sharp whisper-node
```
Ensure native modules are installed and compatible.
Produce a release summary:
- Suggested version bump (patch/minor/major) based on changes
- Draft CHANGELOG entry
- Any blockers or risks identified
- Confirmation: "Ready for release" or "Not ready -- [reasons]"

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.

8d ago First seen · 55 lines · 0 tokens per session scan A 0a11e9694b5c

Subscribe to this mod's changes

release-check is a command published in the GitHub repository eddiesanjuan/markupr (18 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 379 tokens. 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.

Git and workflow Releases ai-agents developer-tools electron transcription voice-recording whisper

markupr: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Pre-Release Checklist

Instructions

What this file has done since we first saw it

Other commands, from other repositories

land-and-deploy

ng-ship-review

release-tag

release

create-release-note.en

post-release.en