A release-readiness testing workflow that checks a feature-by-feature and platform-by-platform coverage table against a real Pi environment. It produces a ship, ship-with-caveats, do-not-ship, or blocked decision based on recorded evidence.

It is for checking whether a build is ready before creating a release tag, including documenting evidence, skipped checks, and counted test coverage.

It prevents a release from being approved merely because tests ran or a log file exists, and exposes cases that were never actually checked.

How apmantza/pi-lens configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to apmantza/pi-lens. 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/apmantza/pi-lens/master/.claude/skills/release-qa/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/apmantza/pi-lens

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/skills/apmantza/pi-lens/release-qa/github.svg)](https://agentmods.dev/skills/apmantza/pi-lens/release-qa)

Your own site

<a href="https://agentmods.dev/skills/apmantza/pi-lens/release-qa"><img src="https://agentmods.dev/badge/skills/apmantza/pi-lens/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/skills/apmantza/pi-lens/release-qa"><img src="https://agentmods.dev/badge/skills/apmantza/pi-lens/release-qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,771 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.00065	$0.02771
Opus 5.5	$0.00026	$0.01108
Sonnet 5.5	$0.00013	$0.00554
Haiku 4.5	$0.00006	$0.00277

Measured 10d ago against content hash 7eaf20cfae47, 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 10d 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/skills/release-qa/SKILL.md · 210 lines

How it starts

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

Release QA

The pass that runs before a release is cut. Sibling of the merge policy (docs/pi-lens-merge-policy.md): that policy decides whether one PR may land, this one decides whether the accumulated result may ship.

Why it exists: #2587. Four shipped skills were suspected of never registering for four releases (3.8.51 → 4.1.3) because no check ever asked a real pi what it loaded. The unit suite (~10.8k tests) and the nightly smokes (install, compat, tool, lifecycle, parser) are per-seam; nothing composed them into a release verdict with counted coverage, so a missing row read as absence rather than arithmetic.

Hard rules

These outrank convenience, habit, and the shape of any previous pass.

No witness, no verdict. A row is PASS only when an artifact SHOWS the pass criterion. A witness that merely exists — a log file that was written, a process that exited 0 — is not a witness. Quote the line.
Reachability is decided in planning, not discovered mid-run. A row that cannot be reached in this run is SKIPPED with the reason written down BEFORE the run, never a PASS that quietly measured nothing.
Coverage is counted, never claimed. Report the discovered / rows / untested arithmetic the runner prints, verbatim. "All the important paths were checked" is not a coverage statement.
An expired poll is UNTESTED, never PASS. Async rows are polled to a terminal state under a stated cap. Expiry means you did not see the result.
BLOCKED is not a failure and not a pass. If pi cannot boot, no ship verdict is issued at all. Say BLOCKED and stop.
The repo's runbook outranks habit. docs/release-qa-baseline.md, docs/pi-lens-release.md and AGENTS.md are the contract. If a step here disagrees with them, they win and this file is wrong.

Procedure

1. Read the baseline

docs/release-qa-baseline.md is the matrix — row ids, entry points, pass criteria, witness kinds. Read it before running anything; the runner parses this same document, so a row you cannot explain is a row the runner will execute anyway.

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

10d ago Changed 7eaf20cfae47
1mo ago Changed · +3 lines 764c069d62ae
1mo ago Changed a48cf37bba7f
1mo ago Changed · +5 lines f5ec4c6b6eca
1mo ago Changed · +6 lines b2ad7c5037c0
1mo ago Changed · +1 lines deb4d343a4b7
2mo ago First seen · 195 lines · 65 tokens per session scan A f3d4e68ea3be

Subscribe to this mod's changes

release-qa is a skill published in the GitHub repository apmantza/pi-lens (514 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 2,771 once invoked, about $0.0003 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-09-07.

Git and workflow Releases Testing

release-qa next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-qaapmantza/pi-lens	Skill	514	yesterday	MIT	A	65	Claude Code
release-announcementpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	yesterday	Apache-2.0	A	22	Claude Code, Codex

pi-lens: Skill for Claude Code