testing-regression-strategy
Testing Regression Strategy
Overview
Use this skill to select regression coverage that maximizes risk reduction within execution constraints.
Scope Boundaries
- Use when not all tests can run every change and selection policy is required.
- Typical requests:
Optimize regression coverage under CI time budget.Define mandatory versus conditional suites by risk.Map change impact to regression gates.
- Do not use when:
- The task is implementing one specific test case only.
- The task is observability/alert policy design (
observability-*).
Inputs
- Release risk profile and CI budget
- Test inventory with cost, flakiness, and detection value
- Change-impact and component criticality model
Outputs
- Tiered regression policy (always-run, conditional, periodic)
- Decision record for suite selection logic and trade-offs
- Verification checklist and gap register
Workflow
- Classify system areas by business and technical risk.
- Quantify each suite by execution cost and detection value in
assets/regression-tiering-template.csv. - Compare selection policies and choose one with rationale.
- Define trigger rules for conditional suites.
- Publish policy, residual risk, and review cadence.
Quality Gates
- High-risk areas are always covered by mandatory gates.
- Selection policy is explainable and auditable.
- Budget trade-offs are explicit, not implicit.
- Policy includes periodic recalibration triggers.
Failure Handling
- Stop when high-risk areas are uncovered by mandatory tests.
- Escalate when budget and required risk coverage conflict.
Bundled Resources
references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.assets/regression-tiering-template.csv: quick-start matrix for always/conditional/nightly suite selection.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9