.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Produce a QA release sign-off / go-no-go readiness report. An agent skill from mohitagw15856/pm-claude-skills.
Install QA Release Signoff
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-release-signoff --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qa-release-signoff .claude/skills/qa-release-signoff && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "qa-release-signoff" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-release-signoff into .claude/skills/qa-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-release-signoff", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-release-signoffType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-release-signoff --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qa-release-signoff .agents/skills/qa-release-signoff && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qa-release-signoff" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-release-signoff into .agents/skills/qa-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-release-signoff", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-release-signoff --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qa-release-signoff .cursor/skills/qa-release-signoff && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "qa-release-signoff" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-release-signoff into .cursor/skills/qa-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-release-signoff", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/qa-release-signoff--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-release-signoff --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qa-release-signoff .gemini/skills/qa-release-signoff && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "qa-release-signoff" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-release-signoff into .gemini/skills/qa-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-release-signoff", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills qa-release-signoffInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qa-release-signoff .github/skills/qa-release-signoff && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "qa-release-signoff" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-release-signoff into .github/skills/qa-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-release-signoff", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-release-signoff --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qa-release-signoff .opencode/skills/qa-release-signoff && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "qa-release-signoff" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-release-signoff into .opencode/skills/qa-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-release-signoff", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
qa-release-signoff- GitHub stars
- 1.4k
- Token cost
- ~926 tokens
- SKILL.md length
- 455 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce a QA release sign-off / go-no-go readiness report. An agent skill from mohitagw15856/pm-claude-skills.
- Asked for a release sign-off
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A go/no-go QA report
What it does
QA Release Signoff is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Feature launches and release readiness. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked for a release sign-off
- A go/no-go QA report
- Release readiness
- A test summary before shipping
Example prompts
- “/qa-release-signoff”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
QA Release Signoff loads about 926 tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 455 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 455 words, ~926 tokens.
Download SKILL.mdSave it as
.claude/skills/qa-release-signoff/SKILL.md (or your agent's skills folder).- name
- qa-release-signoff
- description
- 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.
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]
- Recommendation — Go / Go with conditions / No-go, in one line, up front, with the headline reason.
- Scope — what's in this release.
- Testing summary — what was tested (areas + test types), results (pass/fail, pass rate), and what was not tested.
- Open defects — a table by severity, with impact and any workaround:
| ID | Severity | Area | Impact | Workaround | Blocker? |
|---|
- Coverage & residual risk — what's well-covered vs. thin, and the honest risk of shipping now.
- Conditions to ship (if "go with conditions") — what must be true/fixed/monitored before or right after release.
- Rollback / mitigation — how to undo or contain it (rollback, feature flag, hotfix path) if something goes wrong.
- Sign-off — who's recommending, and what they're attesting to.
Show full SKILL.md (172 more words)Show less
Quality Checks
- The go/no-go recommendation is explicit and up front, with the reason
- Both what was tested and what wasn't are stated — no false sense of coverage
- Open defects are listed by severity with impact and blocker status
- Residual risk is stated honestly, not buried
- "Go with conditions" lists concrete, checkable conditions
- A rollback/mitigation path is included; no results are invented
Anti-Patterns
- Do not give a thumbs-up with no evidence — sign-off is a record, not a vibe
- Do not hide untested areas or thin coverage — that's the risk the reader needs
- Do not conflate severity and priority, or omit blocker status on open bugs
- Do not recommend "go" while ignoring a known critical defect without naming the risk/decision
- Do not ship without a rollback/mitigation note for when it goes wrong
Based On
Release-management & QA practice — evidence-based go/no-go sign-offs with coverage transparency, defect triage, residual-risk disclosure, and rollback planning.
Example Trigger Phrases
- "Write the release sign-off."
- "Give me a go or no-go QA report."
- "Are we release ready?"
- "Summarise testing before we ship."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/qa-release-signoff of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
QA Release Signoff next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| QA Release Signoff this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~926 | Automated safety check: Pass | MIT | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about QA Release Signoff
What does QA Release Signoff do?
Produce a QA release sign-off / go-no-go readiness report. An agent skill from mohitagw15856/pm-claude-skills. QA Release Signoff is an agent skill from mohitagw15856/pm-claude-skills. Produce a QA release sign-off / go-no-go readiness report.
When should I use QA Release Signoff?
QA Release Signoff fits situations like: asked for a release sign-off; A go/no-go QA report; release readiness; A test summary before shipping.
How do I install QA Release Signoff in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a claude-code`. Or copy the skill folder (skills/qa-release-signoff in mohitagw15856/pm-claude-skills) into .claude/skills/qa-release-signoff in your project. Claude Code loads it when a task matches its description.
How do I install QA Release Signoff in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a codex`. Or copy the skill folder (skills/qa-release-signoff in mohitagw15856/pm-claude-skills) into .agents/skills/qa-release-signoff in your project. Codex loads it when a task matches its description.
Can I use QA Release Signoff in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill qa-release-signoff -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qa-release-signoff, .gemini/skills/qa-release-signoff, .github/skills/qa-release-signoff and .opencode/skills/qa-release-signoff in your project.
What does QA Release Signoff need to run?
SKILL.md names no scripts, command-line tools or credentials: QA Release Signoff is instructions for the agent only.
Does QA Release Signoff access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is QA Release Signoff safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does QA Release Signoff use?
QA Release Signoff is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does QA Release Signoff use?
About 926 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to QA Release Signoff?
Skills that share tags, products or a category with QA Release Signoff: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains QA Release Signoff?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.