Critical Path Testing Skill

Identify and prioritize critical code paths using semantic risk scoring.

Updated Mar 19, 2026

Search Tags:#planning #test-generation #integration-tests #risk-analysis #memory-patterns #critical-path-testing

Ready to run

npx skills add https://github.com/drdanmaggs/rocket-fuel --skill critical-path-testing-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Critical Path Testing Skill
Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/critical-path-testing
Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill critical-path-testing-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Identifies and prioritizes the most impactful code paths in a codebase using semantic risk analysis, enabling teams to focus testing on high-risk areas rather than chasing broad coverage.

Core Features & Use Cases

Risk-based prioritization of critical paths using domain-aware scoring.
End-to-end orchestration of a multi-phase workflow (discovery, planning, generation, validation, pattern learning).
Production-ready test generation that leverages test-fixer memory and enforces mandatory patterns.
Memory-driven improvements and proactive backlog planning for future risks.

Quick Start

Run the Critical Path Testing Skill to analyze your codebase and generate production-ready tests for identified critical paths.

Frequently Asked Questions about Critical Path Testing Skill

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

FAQPage Schema

How do I prioritize integration tests for high-risk code paths in my repository?▼

To prioritize integration tests for high-risk code paths, this skill applies semantic risk scoring to identify impactful areas and generates a structured plan detailing test strategies, required fixtures, and dependencies for production-ready test generation.

What is risk-based critical path testing and how does it work?▼

Risk-based critical path testing evaluates code paths using domain-aware semantic scoring to target high-impact areas rather than chasing broad coverage. It orchestrates a multi-phase workflow spanning discovery, planning, generation, validation, and pattern learning.

How do I automate test generation for critical code paths while enforcing mandatory patterns?▼

Automating test generation for critical code paths is handled by returning a structured plan that enforces mandatory patterns and leverages test-fixer memory. It recommends the appropriate model, such as Sonnet or Haiku, for automated integration test generation.

Can I use semantic risk analysis to improve CI stability and plan for future testing backlogs?▼

Semantic risk analysis improves CI stability by providing a dedicated plan for memory patterns and proactive backlog planning. It identifies future risks across the repository to ensure continuous, memory-driven improvements for your integration tests.

Does critical path testing require specific dependencies to run in my environment?▼

Critical path testing requires no external dependencies to function. It operates independently to analyze your codebase and output a structured testing plan detailing files, strategies, fixtures, and recommended models for automated generation.

What is the best way to generate production-ready tests for critical paths instead of chasing broad coverage?▼

The best way to generate production-ready tests for critical paths is using semantic risk scoring to focus on high-priority files. This approach avoids broad coverage by orchestrating targeted discovery, planning, generation, and validation workflows.