skills.rest
sumithr
sumithrCOMMUNITY
Explore all skills by this author →
GitHub

sumo-qa-strategising

Produce a risk-prioritised QA strategy from repository structure and test evidence.

5|1|Updated May 12, 2026
Search Tags:#tdd#mutation testing#test pyramid#repo audit#risk prioritization#qa strategy#ci coverage gates
One-click install
npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-strategising
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sumo-qa-strategising
Source: https://github.com/sumithr/sumo-qa/tree/main/skills/sumo-qa-strategising
Command: npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-strategising

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns ambiguous “make it better” QA requests into a repo-anchored, risk-prioritised testing strategy with measurable gates and clear execution phases.

Core Features & Use Cases

  • Repo-first inventory: walks the actual codebase (services, modules, test dirs, CI, coverage evidence) before proposing any approach.
  • Risk prioritisation by evidence: identifies per-area risks tied to real file paths and testing coverage shape, then prioritises by risk × gap.
  • Phase-by-phase rollout with gates: designs a test pyramid and phased plan where each phase has observable entry and exit criteria, ending with residual risks.

Quick Start

Ask the AI to “Design our QA strategy for this repository, including a risk-prioritised test plan and a phased rollout with entry/exit gates.”

Frequently Asked Questions about sumo-qa-strategising

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

FAQPage Schema
How do I create a risk-prioritised QA strategy from an existing repository?▼

To create a risk-prioritised QA strategy, walk the actual codebase to inventory services, modules, and CI coverage evidence, then identify per-area risks and prioritize QA investment by risk multiplied by testing gap.

What is the best way to design a test pyramid for a complex codebase?▼

Designing a test pyramid requires walking the repository structure to map current tests, then shaping the pyramid layers based on evidence-backed per-area risks and measurable entry and exit criteria for each rollout phase.

How do I audit test coverage and prioritize QA investment across multiple services?▼

Auditing test coverage across services involves a repo walk using host file tools to inventory CI coverage evidence, followed by section-by-section confirmation gates from initial inventory through to identifying residual testing risks.

Can I use this QA strategy approach for a repo audit without adding new dependencies?▼

Yes, this QA strategy approach requires no external dependencies, relying solely on host file tools to perform the repository walk and analyze existing test evidence to produce a phased rollout plan.

When should I use mutation testing and TDD gates in my QA strategy?▼

Mutation testing and TDD gates should be integrated when designing a risk-prioritised QA plan, ensuring each phase of the test pyramid rollout includes observable entry and exit criteria to validate coverage improvements.

Related Skills

Explore More Software Engineering Skills→
amotion-aiamotion-ai

test

Run backend pytest suites and Vite frontend builds to detect regressions.

Official
Intermediate
rabbicserabbicse

test-strategy

Generate a multi-quarter QA strategy document with risk-based prioritization and test pyramid analysis.

Community
Advanced
apassuelloapassuello

running-mutation-tests

Generate mutations, run tests, and report mutation scores.

Community
Intermediate
n4igmen4igme

mtest

Coordinate phase-driven mobile security testing workflows for Android and iOS.

Community
Advanced