risk-based-testing · proffesor-for-testing — Claude Code skill: what it does, how to install
risk-based-testing directs QA effort to high-risk areas using a 1-5 probability and impact scale, adjusting test depth dynamically.
MIT 128 installs ★ 533 updated 2026-10-25
npx skills add proffesor-for-testing/agentic-qe --skill risk-based-testing -a claude-codeWhat risk-based-testing does
The skill scores components by multiplying probability and impact ratings on a 1 to 5 scale. Critical scores (20–25) receive 60% of the testing budget, high risk (12–19) takes 25%, medium (6–11) gets 10%, and low risk (1–5) receives 5% for smoke tests.
Execution coordinates four agents: qe-regression-risk-analyzer, qe-test-generator, qe-production-intelligence, and qe-quality-gate. It relies on a gradient boosting model to forecast risk scores using code complexity, change frequency, author experience, and file age.
Scores update dynamically. A production incident immediately raises the failure probability for affected features, shifting them into deeper test suites. Without historical bug databases and commit logs, the machine learning risk model cannot calculate file-level risk predictions.
What it helps with
- prioritize test coverage for release planning
- allocate automation effort based on failure probability and impact
- adjust component risk scores dynamically after production incidents
- filter test execution in CI/CD pipelines by risk thresholds
Example prompts for the agent
- Assess component risk for payment and search features and generate test plans
- Update risk scores for search after the recent production incident
- Coordinate qe-test-generator to apply comprehensive depth to checkout
How to install risk-based-testing
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill risk-based-testing -a claude-code2Manually: put the files in place
~/.claude/skills/risk-based-testing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/risk-based-testing/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill risk-based-testing -a codex2Manually: put the files in place
.agents/skills/risk-based-testing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill risk-based-testing -a cursor2Manually: put the files in place
.cursor/skills/risk-based-testing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install proffesor-for-testing/agentic-qe assets/skills/risk-based-testing2Manually: put the files in place
.github/skills/risk-based-testing/SKILL.md1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill risk-based-testing -a gemini-cli2Platform CLI
gemini skills install https://github.com/proffesor-for-testing/agentic-qe --path assets/skills/risk-based-testingManually: put the files in place
.devin/skills/risk-based-testing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill risk-based-testing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about risk-based-testing
How do I install risk-based-testing in Claude Code?
Run npx skills add proffesor-for-testing/agentic-qe --skill risk-based-testing -a claude-code. The file will be saved to ~/.claude/skills/risk-based-testing/SKILL.md.
What is the effort allocation formula?
It allocates 60% of testing effort to critical items, 25% to high priority, 10% to medium, and 5% to low-risk areas.
Which subagents does this skill coordinate?
It orchestrates qe-regression-risk-analyzer, qe-test-generator, qe-production-intelligence, and qe-quality-gate sequentially.
Source text
SKILL.md · MIT
---
name: risk-based-testing
description: "Focus testing effort on highest-risk areas using risk assessment and prioritization. Use when planning test strategy, allocating testing resources, or making coverage decisions."
category: testing-methodologies
priority: high
tokenEstimate: 1000
agents: [qe-regression-risk-analyzer, qe-test-generator, qe-production-intelligence, qe-quality-gate]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-02
dependencies: []
quick_reference_card: true
tags: [risk, prioritization, test-planning, coverage, impact-analysis]
trust_tier: 3
validation:
schema_path: schemas/output.json
validator_path: scripts/validate-config.json
eval_path: evals/risk-based-testing.yaml
---
# Risk-Based Testing
<default_to_action>
When planning tests or allocating testing resources:
1. IDENTIFY risks per component (use 1-5 scale for probability and impact)
2. PRIORITIZE: Critical (20+) → High (12-19) → Medium (6-11) → Low (1-5)
3. ALLOCATE effort: 60% critical, 25% high, 10% medium, 5% low
4. REASSESS continuously: Production incidents raise risk; stable code lowers it
</default_to_action>
## Quick Reference Card
### When to Use
- Planning sprint/release test strategy
- Deciding what to automate first
- Allocating limited testing time
- Justifying test coverage decisions
### Effort Allocation by Risk Score
| Score | Priority | Effort | Action |
|-------|----------|--------|--------|
| 20-25 | Critical | 60% | Comprehensive testing, multiple techniques |
| 12-19 | High | 25% | Thorough testing, automation priority |
| 6-11 | Medium | 10% | Standard testing, basic automation |
| 1-5 | Low | 5% | Smoke test, exploratory only |
---
## Apply Test Depth by Risk
```typescript
await Task("Risk-Based Test Generation", {
critical: {
features: ['checkout', 'payment'],
depth: 'comprehensive',
techniques: ['unit', 'integration', 'e2e', 'performance', 'security']
},
high: {
features: ['auth', 'user-profile'],
depth: 'thorough',
techniques: ['unit', 'integration', 'e2e']
},
medium: {
features: ['search', 'notifications'],
depth: 'standard',
techniques: ['unit', 'integration']
},
low: {
features: ['admin-panel', 'settings'],
depth: 'smoke',
techniques: ['smoke-tests']
}
}, "qe-test-generator");
```
### Step 3: Reassess Dynamically
```typescript
// Production incident increases risk
await Task("Update Risk Score", {
feature: 'search',
event: 'production-incident',
previousRisk: 9,
newProbability: 5, // Increased due to incident
newRisk: 15 // Now HIGH priority
}, "qe-regression-risk-analyzer");
```
---
## ML-Enhanced Risk Analysis
```typescript
// Agent predicts risk using historical data
const riskAnalysis = await Task("ML Risk Analysis", {
codeChanges: changedFiles,
historicalBugs: bugDatabase,
prediction: {
model: 'gradient-boosting',
factors: ['complexity', 'change-frequency', 'author-experience', 'file-age']
}
}, "qe-regression-risk-analyzer");
// Output: 95% accuracy risk prediction per file
```
---
## Agent Coordination Hints
### Memory Namespace
```
aqe/risk-based/
├── risk-scores/* - Current risk assessments
├── historical-bugs/* - Bug patterns by area
├── production-data/* - Incident data for risk
└── coverage-map/* - Test depth by risk level
```
### Fleet Coordination
```typescript
const riskFleet = await FleetManager.coordinate({
strategy: 'risk-based-testing',
agents: [
'qe-regression-risk-analyzer', // Risk scoring
'qe-test-generator', // Risk-appropriate tests
'qe-production-intelligence', // Production feedback
'qe-quality-gate' // Risk-based gates
],
topology: 'sequential'
});
```
---
## Integration with CI/CD
```yaml
# Risk-based test selection in pipeline
- name: Risk Analysis
run: aqe risk-analyze --changes ${{ github.event.pull_request.files }}
- name: Run Critical Tests
if: risk.critical > 0
run: npm run test:critical
- name: Run High Tests
if: risk.high > 0
run: npm run test:high
- name: Skip Low Risk
if: risk.low_only
run: npm run test:smoke
```
---
## Related Skills
- [agentic-quality-engineering](../agentic-quality-engineering/) - Risk-aware agents
- [context-driven-testing](../context-driven-testing/) - Context affects risk
- [regression-testing](../regression-testing/) - Risk-based regression selection
- [shift-right-testing](../shift-right-testing/) - Production informs risk
---
## Remember
**With Agents:** Agents calculate risk using ML on historical data, select risk-appropriate tests, and adjust scores from production feedback. Use agents to maintain dynamic risk profiles at scale.
© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe
Similar skills
All skills for Testing and QA →risk-based-testing by other authors comes first.