PEpetrkindlmannqa-skills1,600 installs on skills.sh

Release Readiness

Validate release readiness with evidence-based go/no-go decisions.

Use in my agent
Use Edge to load the skill release-readiness from petrkindlmann/qa-skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
Works in any agentClaude CodeCodexCursorClaude appChatGPT+ any other agent
petrkindlmann/qa-skills
Security state: reviewed

2 static scans, 0 counted findings.

Edge checks it again each time your agent loads it.

SKILL.md3 files · 29.1 KB

From the petrkindlmann public repository. Edge did not write or edit this skill.

What it does

  • Validate release readiness with evidence-based go/no-go decisions.
  • Covers go/no-go checklists, smoke test suite design, staged rollout validation, rollback criteria and procedures, and post-deployment verification.
  • Ensures release confidence comes from data, not feelings.
  • Use when: "release ready," "go/no-go," "smoke test," "release checklist," "rollback plan," "staged rollout," "canary deploy." Not for: safe-release techniques (flags, canary, dark launch) applied during the rollout itself : use testing-in-production; scheduled probes that run continuously after release : use synthetic-monitoring; designing new tests from prod telemetry : use observability-driven-testing.
  • Related: testing-in-production, qa-metrics, ci-cd-integration, ai-system-testing.

How it works

  1. 1
    Copy

    Try for free gives you one prompt.

  2. 2
    Paste

    Paste it into Claude Code, Codex or Cursor.

  3. 3
    Ask

    Ask for the outcome. Your agent loads Release Readiness.

Related skills

PE
Performance Testing
petrkindlmann

Test application performance with k6 load/stress/soak/spike scripts and k6 scenarios, Lighthouse CI for Web Vitals, and performance budgets as CI gates. Covers load profiles, custom metrics, bottleneck identification, an

TA
Gplay Rollout Management
tamtom

Staged rollout orchestration and monitoring for Google Play releases. Use when implementing gradual release strategies.

AD
Shipping and Launch
addyosmani

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a st

+4.2K installs this week
PE
AI Bug Triage
petrkindlmann

Hybrid fingerprint + LLM pipeline for bug classification, deduplication, and ticket generation. Normalizes CI logs, creates stable fingerprints, clusters near-duplicates, then uses LLM for severity classification and tic

GA
Canary
garrytan

Post-deploy canary monitoring. (gstack)

DO
Release Checklist
donchitos

Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.

Evidence

No evidence record yet

No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-22: reviewed. Static scans check the code, not how well the skill works.

State definitions

Skill details

Security scansReviewed

2 static scans, 0 counted findings. Security state at 2026-11-22: reviewed. Edge checks it again each time your agent loads it.

Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.

Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.

Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.

Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.

Edge static checks
Pass · 0 counted findings · 2026-11-22
Edge committed-secret checks
Pass · 0 counted findings · 2026-11-22
Creator, source & licencepetrkindlmann

From the petrkindlmann public repository. Edge did not write or edit this skill.

Revision
b3bb61bd268b147476252c6ed5a0440c87b97441
Package hash
sha256:90e762f03e1c5d44cbc3188a5aa69abba112393b705425ea3bf67d2dd59b61ad
Licence
MIT
Description
Validate release readiness with evidence-based go/no-go decisions. Covers go/no-go checklists, smoke test suite design, staged rollout validation, rollback criteria and procedures, and post-deployment verification. Ensures release confidence comes from data, not feelings. Use when: "release ready," "go/no-go," "smoke test," "release checklist," "rollback plan," "staged rollout," "canary deploy." Not for: safe-release techniques (flags, canary, dark launch) applied during the rollout itself : use testing-in-production; scheduled probes that run continuously after release : use synthetic-monitoring; designing new tests from prod telemetry : use observability-driven-testing. Related: testing-in-production, qa-metrics, ci-cd-integration, ai-system-testing.
Quoted from the skill’s own description
Read skill files3 files

3 files, 29.1 KB at revision b3bb61bd268b.

Questions about Release Readiness

What does Release Readiness do?

Validate release readiness with evidence-based go/no-go decisions. Published by petrkindlmann (petrkindlmann/qa-skills).

Is Release Readiness safe to use?

Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 22, 2026). The Evidence tab shows the scan.

How do I use Release Readiness in Claude Code, Codex or Cursor?

Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.