qa-release-signoff
Produce a QA release sign-off / go-no-go readiness report. Use when asked for a release sign-off, a go/no-go QA report, release readiness, or a test summary before shipping. Produces a sign-off — what was tested and the results, open defects by severity, coverage and residual risk, the go/no-go recommendation with conditions, and a rollback note — so the release decision is evidence-based, not a vibe.
npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# QA Release Sign-off Skill A release sign-off turns "QA says it's fine" into an evidence-based decision: here's what we tested, here's what passed and what's still open, here's the risk, and here's the recommendation. This skill produces that report so the go/no-go is accountable — and so anyone reading it later knows exactly what shipped and what didn't. ## Working from a brief Given test results and a list of open bugs, **produce the sign-off anyway** — organise the evidence, weigh the open defects, and make a clear recommendation with conditions, marking anything unverified *(confirm)*. Never invent test results or pass rates; if coverage is thin, say so as a risk. ## Required Inputs Ask for these only if they aren't already provided (else mark unknown / as a risk): - **The release** — what's shipping (version/scope) and the target date. - **Testing done** — what was tested (areas, types), results/pass rate, and what wasn't covered. - **Open defects** — known bugs with severity, and any with workarounds. - **Risk & ops** — known risks, rollback/feature-flag availability, and any acceptance criteria/exit gates. ## Output Format ### QA Sign-off: [release] — [date] - **Recommendat
- Working from a brief
- Required Inputs
- Output Format
- QA Sign-off: [release] — [date]
- Quality Checks
- Anti-Patterns
- Based On
What does the qa-release-signoff skill do?
Produce a QA release sign-off / go-no-go readiness report. Use when asked for a release sign-off, a go/no-go QA report, release readiness, or a test summary before shipping. Produces a sign-off — what was tested and the results, open defects by severity, coverage and residual risk, the go/no-go recommendation with conditions, and a rollback note — so the release decision is evidence-based, not a vibe.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.