regression-planner
npx machina-cli add skill cyberwalk3r/qa-toolkit/regression-planner --openclawRegression Test Planner
Analyze changes and plan targeted regression testing. Read qa-artifacts/.qa-config.json for project context.
Input
Accept via $ARGUMENTS: PR details, release description, list of changed files, or feature area.
Workflow
- Map the change scope — what files/modules changed
- Identify impact radius:
- Direct: features that use the changed code
- Indirect: features that depend on those features
- Shared: utilities, configurations, middleware used across features
- Risk-rank each affected area (High / Medium / Low)
- Generate regression test plan with time estimates
- Recommend scope based on available time:
- Quick (1-2h) — smoke tests on changed + directly affected areas
- Standard (4-8h) — above + integration points and shared components
- Full (1-2 days) — complete regression suite
Output Structure
## Regression Plan: <change description>
Date: YYYY-MM-DD
### Change Summary
<what changed and why>
### Impact Analysis
| Area | Impact | Risk | Reason |
|------|--------|------|--------|
| ... | Direct/Indirect/Shared | High/Med/Low | ... |
### Recommended Test Scope
#### Must Test (P0) — <time estimate>
- [ ] <test area and what to verify>
#### Should Test (P1) — <time estimate>
- [ ] <test area>
#### Nice to Test (P2) — <time estimate>
- [ ] <test area>
### Skip Justification
<areas consciously not tested and why>
For detailed impact analysis heuristics, read references/impact-analysis.md.
Save
Save to qa-artifacts/regression-plans/regression-YYYY-MM-DD-<brief>.md
Suggested Next Steps
After generating the regression plan, suggest:
- "When regression testing is complete, assess release readiness with
/qa-toolkit:release-readiness."
Source
git clone https://github.com/cyberwalk3r/qa-toolkit/blob/main/skills/regression-planner/SKILL.mdView on GitHub Overview
Regression Test Planner analyzes changes and creates targeted regression test plans with time estimates. It reads project context from qa-artifacts/.qa-config.json and outputs a structured plan that captures impact, risk, and recommended scope for testing.
How This Skill Works
Accepts PR details, release notes, and changed file lists via ARGUMENTS. It maps the change scope, identifies Direct, Indirect, and Shared impact radii, ranks risk, and generates a test plan with time estimates. The result is a Regression Plan saved under qa-artifacts/regression-plans.
When to Use It
- When planning regression testing for a PR that touches multiple modules.
- When assessing impact to determine the minimal viable regression scope.
- When time budget is limited and prioritization is needed (Quick/Standard/Full).
- When changes touch core functionality or shared utilities.
- When you want a reproducible, documented regression plan for release readiness.
Quick Start
- Step 1: Provide PR details, release notes, and changed files.
- Step 2: Run regression-planner to generate the Regression Plan.
- Step 3: Review and adjust scope based on time and release readiness.
Best Practices
- Capture precise PR details and changed files to feed ARGUMENTS.
- Consistently classify impact as Direct, Indirect, or Shared.
- Use High/Medium/Low risk labels and justify with reasons.
- Timebox estimates per scope (P0/P1/P2) and adjust for available time.
- Review the plan against the qa-artifacts/config and release readiness steps.
Example Use Cases
- A bug fix touching checkout and payment modules yields a plan prioritizing cart, checkout, and payment API tests with time estimates.
- Auth middleware refactor; plan covers login, session management, and token refresh.
- Shared utilities change used across reports; plan includes regression for reporting and data export.
- Client API version bump; plan targets API compatibility, request/response schemas, and error handling.
- UI dashboard redesign; plan focuses on rendering data widgets and user interactions.
