skills.rest
vadimcomanescu
vadimcomanescuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

senior-qa

Create risk-based QA test strategies and validate software release readiness.

24|8|Updated Jan 14, 2026
Search Tags:#e2e#qa#test-automation#flaky-tests#test-plan#exploratory-testing#risk-based-testing
One-click install
npx skills add https://github.com/vadimcomanescu/codex-skills --skill senior-qa-vadimcomanescu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-qa
Source: https://github.com/vadimcomanescu/codex-skills/tree/main/skills/.curated/quality/senior-qa
Command: npx skills add https://github.com/vadimcomanescu/codex-skills --skill senior-qa-vadimcomanescu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

QA teams and release owners need a practical way to prioritize testing effort, reduce flaky-test risk, and define clear pass/fail criteria so releases ship with measurable confidence and minimal manual overhead.

Core Features & Use Cases

  • Risk-based test strategy: Identify high-risk user journeys and focus testing on money, auth, data loss, and critical flows.
  • Test layer guidance: Decide when to use unit, integration, or E2E tests to get the best confidence per effort.
  • Release test plans & scaffolding: Produce must-pass automated checks, a concise manual checklist, exploratory charters, and a scaffoldable TEST_PLAN.md for project docs.
  • Flakiness triage: Triage flaky tests as product bugs and recommend root-cause actions and mitigation strategies.
  • Use case: Prepare a release sign-off checklist that combines CI gates, E2E smoke, and targeted manual checks for auth and payment flows.

Quick Start

Generate a risk-based release test plan that lists must-pass automated checks, E2E smoke paths, and a concise manual checklist for critical journeys.

Frequently Asked Questions about senior-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a risk-based QA test strategy for a software release?▼

A risk-based QA test strategy identifies high-risk user journeys like money, auth, and data loss flows, then outputs must-pass automated checks and focused manual checklists to validate release readiness with minimal manual overhead.

How do I decide when to use E2E tests versus unit or integration tests?▼

Deciding on E2E tests versus unit or integration tests requires evaluating test layer guidance to maximize confidence per effort, ensuring critical paths are covered without introducing unnecessary flaky test risk in the test suite.

What is the best way to triage flaky tests in an automated test suite?▼

Triage flaky tests by treating them as product bugs, analyzing root causes, and applying mitigation strategies to stabilize E2E smoke paths and automated checks so CI gates pass reliably for release sign-off.

Can I generate a TEST_PLAN.md template with must-pass automated checks for project documentation?▼

You can generate a scaffoldable TEST_PLAN.md template that includes must-pass automated test lists, E2E smoke paths, exploratory testing charters, and concise manual checklists suitable for direct inclusion in project documentation.

How do I prepare a release sign-off checklist that combines CI gates and manual checks?▼

Prepare a release sign-off checklist by combining CI gates, E2E smoke tests, and targeted manual checks for critical journeys like auth and payment flows to ensure measurable confidence before shipping.

What should be included in exploratory testing charters for critical user flows?▼

Exploratory testing charters for critical user flows should include focused objectives for high-risk areas, guiding testers through unscripted validation of complex paths like money and auth journeys identified during risk-based test planning.

Related Skills

Explore More Software Engineering Skills→
heymishyheymishy

coverage-map

Read test plans and pipeline-state.json to report per-story and per-AC coverage status.

Community
Intermediate
patricio0312revpatricio0312rev
5

deployment-checklist-generator

Generate deployment readiness checklists with pre-deployment checks and approval gates.

Community
Advanced
hopeoverturehopeoverture
6

github-actions-ci-workflow

Generate GitHub Actions CI/CD workflows for web apps with lint, test, build, and deploy pipelines.

Community
Advanced
OmexITOmexIT
13

test-plan

Create risk-based markdown test plans for features, PRs, or releases.

Community
Intermediate