Release Testing Workflow

naodeng/release-testing-workflow

Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.

9k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

144

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/naodeng/awesome-qa-skills --skill release-testing-workflow

What comes with it

35 157 bytes besides the instruction

README.md

agents/openai.yaml

evals/cases/basic-success.yaml

evals/cases/edge-gates-handoff.yaml

evals/cases/edge-incomplete-input.yaml

evals/eval.yaml

output-templates/template-csv.csv

output-templates/template-excel.tsv

output-templates/template-json.json

output-templates/template-markdown.md

output-templates/template-word.md

output-templates/template-xmind.md

prompts/release-testing-workflow.md

reference.md

scripts/batch_convert_templates.py

scripts/convert_formats.py

scripts/convert_output_formats.py

scripts/convert_to_csv.py

scripts/convert_to_excel.py

scripts/convert_to_json.py

scripts/convert_to_markdown.py

scripts/convert_to_word.py

scripts/convert_to_xmind.py

scripts/parse_csv.py

scripts/parse_excel.py

scripts/parse_formats.py

scripts/parse_json.py

scripts/parse_markdown.py

scripts/parse_output_formats.py

scripts/parse_word.py

scripts/parse_xmind.py

The instruction itself

7 sections, as written by the author

Release Testing Workflow

中文版： See the corresponding Chinese skill.

When to Use

Need a release-window cadence: T-N planning → specialties → RC → Go/No-Go → post-release watch.
Need release gates and a ship evidence pack, with specialty execution handed to type skills.

Workflow

Read and follow prompts/release-testing-workflow.md (timeline, gates, Go/No-Go, handoffs).
Add release date, scope, freeze rules, candidate build, and known defects that change decisions.
After locating the T window, hand off by skill name per reference.md; invoke specialty type skills by name only.
If input is incomplete, still draft a gate board and mark assumptions—never invent pass results.

Core Constraints

Own release timeline and ship decision; hand specialty reports to performance-testing / security-testing / etc.
Timelines may compress; gate criteria may not be deleted.
Go/No-Go requires evidence; conditional Go must be verifiable.
No relative-path links to other skill files.

Progressive Disclosure

Before producing output, read and follow prompts/release-testing-workflow.md.
For step ↔ handoff mapping: read reference.md.
For stage/specialty deep-dives: invoke the matching type skill; do not expand full specialty reports here.
Templates: output-templates/.

Pre-delivery Checklist

[ ] Followed the main prompt’s output structure
[ ] Includes scope/exclusions, T window, gate board, evidence gaps, next skill
[ ] At decision point: Go / No-Go / conditional with rationale
[ ] Did not invent pass results or unknown defect states
[ ] Assumptions and open questions are marked

Common Pitfalls

Do not delete gates just to compress the calendar.
Do not declare RC done before freeze.
Do not write full specialty long-reports inside this skill.
Do not replace conditional-Go terms with vague “keep watching”.

How to use it

Copy the folder

Take naodeng/release-testing-workflow from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.