agentsclimarketplace

Test

10,621 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Skill tdd

    Moliboy5000/.claude/plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-tdd Skill

    no license0★ repo

    Build features with tests-before-code rigor — use for new features needing test coverage. Use when: Use when implementing any feature, bugfix, or behavior change.. Auto-invoke when user says "implement X", "add feature Y", "fix bug Z".

  • Webapp testing

    Moliboy5000/.claude/skills/webapp-testing Skill

    no license0★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Smoke test

    Stoica-Mihai/claude-skills/plugins/quality-assurance/skills/smoke-test Skill

    0★ repo

    Designs and scaffolds smoke-test suites (build-verification tests) for web services, APIs, and software systems. Use this skill whenever the user asks to "add smoke tests", "set up build verification", "write a fast test that proves the deploy isn't broken", "what should my smoke tests cover", "wire smoke tests into CI", or anything else about catching catastrophic failures before downstream testing. Also trigger on "BVT / BAT", "intake testing", "sanity vs smoke", "build acceptance". The skill detects the project's stack (Python/FastAPI, Node/Express, Go net/http, Rust/axum, etc.), proposes a focused 5-10 check suite following the API-first, <2-minute, idempotent discipline, and emits a runnable scaffold in the right framework — with `TODO` markers for environment-specific values like base URL and auth tokens. Even if the user has not explicitly said "smoke", trigger when they ask for a "fast CI gate", "deploy-readiness check", "is-the-build-up test", "happy-path coverage", or describe symptoms like "we keep running a 20-minute regression suite against broken builds".

  • Tdd

    Stoica-Mihai/claude-skills/plugins/tdd/skills/tdd Skill

    0★ repo

    Test-Driven Development workflow. Use when the user asks to work test-first, says "tdd", "/tdd", "write tests first", "red green refactor", "test-driven", or explicitly wants failing tests before implementation. Also trigger when the user says "add tests for X then implement" or "start with a test". Do NOT trigger on general coding requests that don't mention test-first intent.

  • Testing strategy

    thetruong1099/android-mvi-base-code/.claude/skills/testing-strategy Skill

    no license0★ repo

    Testing patterns for this project. Use when writing ViewModel unit tests with MainDispatcherRule and MockK, UseCase tests mocking repositories, Repository tests with data source mocks, or Compose UI tests with FakeBaseViewModel and TemplateThemePreview. Covers Google Truth assertions and test naming conventions.

  • Plan

    crustacean-dev/knowledge-skills/skills/plan Skill

    0★ repo

    Create technical architecture and planning documents. Two modes — project-level (produces .knowledge/architecture.md + .knowledge/conventions.md with directory structure, package dependencies, build pipeline, testing strategy, coding conventions, commit format, CI/CD) and feature-level (produces .knowledge/features/<feature>/plan.md + api/*.d.ts TypeScript contracts with exact data models, integration maps, and architectural decisions). Every decision includes a rejected alternative with rationale. Use this skill whenever the user wants to plan architecture, define conventions, structure a project, design how a feature should be built technically, figure out package layout or module boundaries, establish coding standards, or determine build/test/CI workflows. Trigger on "plan", "plan <feature>", "architecture", "conventions", "how should we build this", "design the system", "structure the project", "what should the technical approach be", "figure out the data model", or any request to make technical decisions before implementation begins. Requires .knowledge/constitution.md to exist — if missing, redirects to /constitution. Does NOT produce specs (user-facing behavior), tasks (implementation breakdown), or code (implementation). Does NOT read or summarize existing documents — it creates new planning artifacts through a structured interview.

  • Review

    crustacean-dev/knowledge-skills/skills/review Skill

    0★ repo

    Code review — check if implementation matches specs, conventions, and constitution. Use this skill ANY time the user wants to verify, check, audit, or review code that has been written. This includes explicit requests like "review", "review TASK-3", "review auth", "code review" AND indirect requests like "check my work", "check the code", "does this match the spec", "does this follow conventions", "is this clean", "sanity check", "look over the code", "did I miss anything", "any violations", "is the implementation correct", "can we merge this", "is TASK-N done", "are there constitution violations", "check test coverage". ALSO trigger after /implement completes to suggest a review. ALSO trigger when user mentions checking code against knowledge files, acceptance criteria, or convention conformity. This skill reads code and knowledge files, then produces a structured ✅/⚠️/❌ report with file:line references — it never modifies code. Do NOT trigger for spec review (/clarify), writing code (/implement), planning (/plan), task breakdown (/tasks), stress testing (/challenge), refactoring without task context, or adding tests outside a task.

  • Testing

    dewitt4/claude-code-template/.claude/skills/testing Skill

    no license0★ repo

    Generate comprehensive test cases, improve test coverage, and create testing strategies for unit, integration, and e2e tests

  • Tdd pattern

    JLugagne/claude-skills/dev/agile-team-v2/skills/tdd-pattern Skill

    0★ repo

    Use this skill whenever you are running as the `red` or `green` agent on an agile-team-v2 task. Covers the discipline-based spec isolation between red and green (no private TASK*.md files exist; the only handoff is committed code/tests), the in-scope vs out-of-scope rules of the red/green pattern (applies to standard and architectural complexity features only — mechanical maintenance is a mono-agent task), the mono-assistant safeguard when one Claude instance must wear both hats sequentially (commit red first, fresh session before reading green-side material — `check.sh` audits this at sprint review), and the marker-based task lookup procedure (grep for `TODO(impl-<slug>, ac-<NNN>)` to locate the scaffolded body and its sibling test file). Loaded only by `red` and `green`. Other agents (architect, PM, sprint-planner, e2e-tester, reviewer, bug-detective) operate outside the live red/green isolation flow and do not need these rules.

  • Go dev

    JLugagne/claude-skills/dev/go-hexagonal/skills/go-dev Skill

    0★ repo

    Green phase TDD - implements code to make failing tests pass. Never touches test files. Reports disagreements with test expectations.

  • Go test writer

    JLugagne/claude-skills/dev/go-hexagonal/skills/go-test-writer Skill

    0★ repo

    Red phase TDD - writes failing unit tests, contract tests, and e2e API tests. Covers all test levels in a single pass. Never touches implementation code.

  • Testability and automation architecture evaluator

    anyulled/architecture-guardrails-skills/skills/testability-and-automation-architecture-evaluator Skill

    0★ repo

    Evaluate test suite architecture for brittle coupling to implementation details, shared state, and poor seam alignment. Use when reviewing tests, mocking strategies, or integration test isolation.

  • Doc testing

    JLugagne/agach/.claude/skills/doc-testing Skill

    0★ repo

    Agach testing strategy: test contract pattern, mock structure, contract tests, testcontainers with postgres:17, security tests, QA seed data

  • Dba

    mvdmakesthings/skills/plugins/specialist/skills/dba Skill

    no license0★ repo

    Postgres-first DBA workflows — run a full database health audit, design and implement schema (tables, constraints, RLS, indexes, migrations + tests), clean up unused indexes / bloat / dead tuples, diagnose and fix slow queries, and investigate live database incidents (high CPU, lock storms, error spikes, connection exhaustion). Use whenever the user says "audit the database", "DB health check", "design a schema", "model this table", "add a table for X", "clean up indexes", "database bloat", "why is this query slow", "optimize this query", "explain analyze this", "investigate the database", "the DB is on fire", "high CPU on Postgres", "connection pool exhausted", or types "/dba" — even when they don't say the word "DBA" or name a specific workflow. Discovers each project's migration, test, and deploy conventions at runtime rather than assuming them.

  • Gabe feature

    khujta/gabe-suite/skills/gabe-feature Skill

    no license0★ repo

    Feature coverage for a project's Testing Command Center — translate shipped work into its entity's lens card, diagrams, and evidence narration over machine-derived facts, and keep the center regenerating green. Usage: /gabe-feature [<phase>|--range A..B] | status | backfill | curate <artifact-subdir> <shot-nums…> | release [--since <row>]

  • Testing

    ortus-boxlang/skills/boxlang-developer/testing Skill

    no license0★ repo

    Use this skill when writing, running, or debugging tests for BoxLang applications using TestBox: BDD-style describe/it specs, xUnit-style test classes, expectations (expect/toBe matchers), assertions ($assert), life-cycle methods (beforeAll/afterAll/beforeEach/afterEach/aroundEach), MockBox mocking (createMock/prepareMock/$()/$results()), mock data generation (mockData()), async testing, exception testing, focused/skipped specs, and running tests via the BoxLang CLI runner.

  • Commandbox testing

    ortus-boxlang/skills/commandbox/commandbox-testing Skill

    no license0★ repo

    Use this skill for CommandBox TestBox integration: testbox run command, running tests from CLI, configuring runner URL in box.json, multiple output formats (json/antjunit), test watcher (testbox watch), CI integration, code coverage with FusionReactor, test labels and suites, and box.json testbox configuration.

  • Qa test planner

    payals/ai-skills-engine/dot_cursor/skills/ai-research/qa-test-planner Skill

    0★ repo

    Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

    The same file is in 7 other repositories

  • Senior qa

    payals/ai-skills-engine/dot_cursor/skills/development/senior-qa Skill

    0★ repo

    Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup, and quality metrics. Use when designing test strategies, writing test cases, implementing test automation, performing manual testing, or analyzing test coverage.

    The same file is in 5 other repositories

  • Senior security

    payals/ai-skills-engine/dot_cursor/skills/development/senior-security Skill

    0★ repo

    Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.

    The same file is in 4 other repositories

  • Test driven development

    payals/ai-skills-engine/dot_cursor/skills/development/test-driven-development Skill

    0★ repo

    Use when implementing any feature or bugfix, before writing implementation code

    The same file is in 33 other repositories

  • Test fixing

    payals/ai-skills-engine/dot_cursor/skills/development/test-fixing Skill

    0★ repo

    Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

    The same file is in 5 other repositories

  • Testing patterns

    payals/ai-skills-engine/dot_cursor/skills/development/testing-patterns Skill

    0★ repo

    Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.

    The same file is in 4 other repositories

  • Network 101

    payals/ai-skills-engine/dot_cursor/skills/utilities/network-101 Skill

    0★ repo

    This skill should be used when the user asks to "set up a web server", "configure HTTP or HTTPS", "perform SNMP enumeration", "configure SMB shares", "test network services", or needs guidance on configuring and testing network services for penetration testing labs.

    The same file is in 1 other repository

  • Playwright skill

    payals/ai-skills-engine/dot_cursor/skills/utilities/playwright-skill Skill

    0★ repo

    Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

    The same file is in 9 other repositories

  • Testing

    Texarkanine/a16n/packages/cli/test/integration/fixtures/claude-skill-to-cursor/from-claude/.claude/skills/testing Skill

    no license0★ repo

    Testing best practices

  • Testing

    Texarkanine/a16n/packages/plugin-claude/test/fixtures/claude-rules-mixed/from-claude/.claude/skills/testing Skill

    no license0★ repo

    Testing best practices

  • Simple testing

    Texarkanine/a16n/packages/plugin-claude/test/fixtures/claude-skills-complex/from-claude/.claude/skills/simple-testing Skill

    no license0★ repo

    Simple testing guidelines without extra files or hooks

  • Testing

    Texarkanine/a16n/packages/plugin-claude/test/fixtures/claude-skills/from-claude/.claude/skills/testing Skill

    no license0★ repo

    Testing best practices

  • Multiline desc

    Texarkanine/a16n/packages/plugin-claude/test/fixtures/claude-yaml-edge-cases/from-claude/.claude/skills/multiline-desc Skill

    no license0★ repo

    Use TDD when writing tests. Prefer descriptive test names. Handle edge cases.

  • Stress test

    arndvs/ctrlshft/skills/stress-test Skill

    0★ repo

    Invoke to run the adversarial stress test protocol against ctrl+shft rule compliance. Guides a human reviewer through systematic attempts to break rule boundaries — the same methodology a skeptical senior engineer would use before trusting the system in production.

  • Tdd

    arndvs/ctrlshft/skills/tdd Skill

    0★ repo

    Red-green refactor workflow for test-driven development. Use when asked to 'write tests first', 'TDD', 'red-green refactor', 'test-driven', or 'failing test first'. Backend-only — do not use for frontend components.

  • Testing patterns

    RadKod/claude-agents-kit/flutter/.claude/skills/testing-patterns Skill

    no license0★ repo

    Flutter test pattern'leri. ViewModel test, widget test, repository mock. Test yazarken kullan.

  • Verify deployment

    AayushMS/deploy-skills/skills/verify-deployment Skill

    0★ repo

    Use this skill when the user asks to "verify my deployment", "check if everything is working", "test my deployment", "check if my services are up", "run health checks", or when invoked by deploy-project as the final step after CI/CD setup. Reads DEPLOYMENT_DOCS/DEPLOYED_ENV.md for service URLs, runs HTTP health checks on all services, uses agent-browser to visually verify the frontend loads, tests cross-service connectivity (frontend calls backend, backend connects to DB), and prints a pass/fail summary table. Retries Render backend endpoints up to 3 times due to free tier cold starts.

  • Debug

    jessedegans/jstack/skills/debug Skill

    no license0★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Enforces root cause investigation before fixing. No guessing, no shotgun debugging. Hard stop after 3 failed hypotheses. Use when: tests fail, errors appear, behavior doesn't match expectations, or something "just broke."

  • Code reviewer

    Ortus-Solutions/skills/code-reviewer Skill

    no license0★ repo

    Use when performing high-signal code reviews focused on correctness, security, maintainability, performance, and test coverage risk. Invoke for pull request review, architecture drift detection, bug risk assessment, and actionable feedback with severity-ranked findings.

  • Junit expert

    Ortus-Solutions/skills/junit-expert Skill

    no license0★ repo

    Use when writing, reviewing, or structuring JUnit 5 tests for Java applications. Invoke for test lifecycle, parameterized tests, test extensions, assertions, test organization, parallel execution, test suites, dynamic tests, and integration with build tools.

  • Mockito expert

    Ortus-Solutions/skills/mockito-expert Skill

    no license0★ repo

    Use when mocking, stubbing, spying, or verifying collaborator behavior in Java unit tests. Invoke for mock creation, argument matchers, stubbing strategies, verification, argument captors, answer implementations, strict stubbing, spy objects, and Mockito extensions with JUnit 5.

  • Testing with nullables

    msewell/agent-stuff/.archive/skills/testing-with-nullables Skill

    0★ repo

    Guides writing fast, reliable, refactoring-friendly tests using the Nullables pattern language (James Shore's 'Testing Without Mocks'). Produces narrow, sociable, state-based tests with production code that has an infrastructure 'off switch' — no mock frameworks needed. Use when writing tests, replacing mocks with Nullables, making infrastructure code testable, adding createNull() factories, implementing output tracking, wrapping external dependencies, or adopting testing-without-mocks patterns. Covers embedded stubs, configurable responses, behavior simulation, A-Frame architecture, and incremental migration from mock-based test suites.

  • Property based testing with kotest

    msewell/agent-stuff/skills/property-based-testing-with-kotest Skill

    0★ repo

    Writes property-based tests using Kotest's kotest-property module. Identifies testable properties, designs generators, and configures PBT for Kotlin/JVM projects. Use when writing property-based tests, creating custom Arb generators, choosing property patterns (roundtrip, invariant, idempotence, oracle), debugging shrunk counterexamples, or integrating PBT into a Kotlin test suite alongside example-based tests.

  • Tdd with llm agents

    msewell/agent-stuff/skills/tdd-with-llm-agents Skill

    0★ repo

    Enforces strict red/green/refactor TDD discipline when writing code. Guides the agent through one-test-at-a-time cycles, prevents test subversion, and ensures minimal implementation. Use when writing code with TDD, doing test-driven development, implementing features test-first, or when the user mentions red/green TDD, failing tests first, or test-driven workflow.

  • Testing patterns

    chawkitariq/fidely/.claude/skills/testing-patterns Skill

    0★ repo

    Patterns de tests Fidely : Vitest + @nuxt/test-utils + fake-indexeddb + happy-dom. Déclencher quand : écriture de test, ajout composable (useDB, useClient), nouveau composant Vue, modification d'une fonction dans utils/, isolation IndexedDB, mock Nuxt (useToast, navigateTo). Mots-clés : describe, it, expect, beforeEach, IDBFactory, resetDB, mountSuspended, mockNuxtImport, fake-indexeddb, useDB.test.ts, CardItem.test.ts, CardForm.test.ts, updatePoints, consumeReward, addCard, getOrCreateClientId.

  • Rust quality

    dawidpereira/rust-skills/skills/rust-quality Skill

    0★ repo

    Rust code quality — linting, project structure, anti-patterns, and advanced testing tools. Use when configuring clippy lints, organizing modules and workspaces, reviewing code for common Rust anti-patterns like excessive cloning or unwrap abuse, or setting up proptest, mockall, or criterion. Also use when setting up a new Rust project's Cargo.toml with recommended lint and profile settings. For unit and integration test strategy, see rust-tests.

  • Rust tests

    dawidpereira/rust-skills/skills/rust-tests Skill

    0★ repo

    Rust unit and integration test strategy — when to write which kind of test, how to structure test modules, test helpers and builders, error path testing, parameterized tests, integration test organization, binary crate testing, and test isolation. Use when deciding between unit and integration tests, organizing a growing test suite, testing error paths, setting up shared test utilities, or structuring the tests/ directory for a workspace. Also use when tests are slow, brittle, or hard to navigate.

  • Testing base classes

    ColdBox/skills/coldbox/testing-base-classes Skill

    no license0★ repo

    Use this skill to understand which ColdBox testing base class to extend for a given test type, configure test bundle annotations (appMapping, configMapping, unloadColdBox, loadColdBox, coldboxAppKey), set up the tests/ harness (Application.cfc, folder structure), or choose between integration testing (BaseTestCase), isolated handler testing (BaseHandlerTest), model unit testing (BaseModelTest), and interceptor unit testing (BaseInterceptorTest).

  • Testing handler

    ColdBox/skills/coldbox/testing-handler Skill

    no license0★ repo

    Use this skill when testing ColdBox event handlers with execute(), asserting rc/prc collections, verifying view selection and rendered output, mocking relocations, testing renderData() and getHandlerResults(), setting HTTP methods and headers, injecting mocks into handlers, or using BaseHandlerTest for isolated handler unit tests.

  • Testing http methods

    ColdBox/skills/coldbox/testing-http-methods Skill

    no license0★ repo

    Use this skill when simulating HTTP requests in ColdBox tests using the get(), post(), put(), patch(), delete(), or request() methods, setting request headers (Authorization, Accept, Content-Type), sending JSON request bodies, asserting response status with toHaveStatus(), checking validation errors with toHaveInvalidData(), or understanding the difference between execute() (event-based) and the HTTP method helpers (route/URL-based).

  • Testing integration

    ColdBox/skills/coldbox/testing-integration Skill

    no license0★ repo

    Use this skill when writing integration tests for ColdBox that use real dependencies (database, WireBox, ColdBox context), testing full request/response cycles with execute(), setting up and tearing down test databases, testing services with real data, or using BaseTestCase for end-to-end handler tests with actual WireBox injections.

  • Testing interceptor

    ColdBox/skills/coldbox/testing-interceptor Skill

    no license0★ repo

    Use this skill when unit testing ColdBox interceptors in isolation using BaseInterceptorTest, accessing the pre-wired interceptor variable, leveraging mock helpers (mockController, mockRequestService, mockLogger, mockLogBox, mockFlash), configuring interceptor properties with configProperties, calling interceptor announce points directly, or scaffolding interceptor tests with CommandBox.

  • Testing model

    ColdBox/skills/coldbox/testing-model Skill

    no license0★ repo

    Use this skill when unit testing ColdBox model objects (services, repositories, entities, or utility classes) in isolation using BaseModelTest, accessing the pre-wired model variable, leveraging the built-in mock helpers (mockLogger, mockLogBox, mockCacheBox, mockWireBox), calling model.init() to initialize the component, mocking injected properties with prepareMock(), or scaffolding model tests with CommandBox.

  • Cbmockdata

    ColdBox/skills/modules/cbmockdata Skill

    no license0★ repo

    Use this skill when generating realistic fake seed/test data in ColdBox/BoxLang using the cbmockdata module. Covers installation, the mock() API, built-in data types, entity population, testing integration, and bulk generation patterns for prototyping and test suites.

  • Cbplaywright

    ColdBox/skills/modules/cbplaywright Skill

    no license0★ repo

    Use this skill when writing end-to-end browser tests in ColdBox/BoxLang using the cbplaywright module (a Playwright wrapper). Covers test bundle setup, browser/page lifecycle, navigation, selectors, assertions, form interactions, screenshots, network interception, the Page Object pattern, and CI pipeline integration.

  • Bdd

    ColdBox/skills/testbox/bdd Skill

    no license0★ repo

    Use this skill when writing BDD-style tests with TestBox using describe/it blocks, feature/story/scenario/given/when/then Gherkin-style suites, lifecycle hooks (beforeAll/afterAll/beforeEach/afterEach/aroundEach), focused specs (fit/fdescribe), skipping specs (xit/xdescribe/skip()), spec data binding, asyncAll parallel specs, nested suite trees, labels, or organizing tests around behavior descriptions.

  • Runners

    ColdBox/skills/testbox/runners Skill

    no license0★ repo

    Use this skill when running TestBox tests: CommandBox CLI (testbox run), BoxLang CLI (./testbox/run), HTML web runner, programmatic TestBox instantiation (run/runRaw/runRemote), configuring test directories or bundles, using the streaming runner (--stream flag / StreamingRunner), watcher mode, all CLI flags (--show-failed-only, --dry-run, --slow-threshold-ms, --stacktrace, --max-failures), or setting up box.json testbox configuration.

  • Testing coverage

    ColdBox/skills/testbox/testing-coverage Skill

    no license0★ repo

    Use this skill when setting up code coverage analysis for ColdBox/ColdFusion/BoxLang applications, configuring coverage reporting, integrating coverage with CI pipelines, using TestBox coverage options, interpreting coverage metrics, or improving test coverage of untested code paths.

  • Testing fixtures

    ColdBox/skills/testbox/testing-fixtures Skill

    no license0★ repo

    Use this skill when creating test fixtures, factory patterns, or test data builders in ColdBox/TestBox, setting up shared fixture files, creating user/model factories with overrides, using cbMockData for realistic fake data generation, or managing test data setup and teardown.

  • Unit

    ColdBox/skills/testbox/unit Skill

    no license0★ repo

    Use this skill when writing xUnit-style tests in TestBox using test functions (testXxx()), setup/teardown lifecycle (beforeTests/afterTests/setup/teardown), $assert assertion object, or the Arrange-Act-Assert (AAA) pattern for unit testing services, models, and utilities in isolation.

  • Regression testing

    Victoriakaey/build-reliable-agents/skills/regression-testing Skill

    0★ repo

    Use when comparing two versions of an LLM system, debugging non-deterministic behavior, or establishing a baseline before making changes. Covers controlled comparison protocol, determinism verification, and bisect protocol for finding which change caused a regression.

  • Test

    RhythmMittal19/claude-config/skills/test Skill

    0★ repo

    Run tests and analyze failures with actionable fix suggestions.

  • Test gap analyzer

    jsynowiec/claude-toolkit/plugins/stackshift/skills/test-gap-analyzer Skill

    0★ repo

    Identifies which upgrade-affected components lack test coverage and scores risk by crossing change severity with coverage level. Use when planning an upgrade to flag risky untested paths before making changes.