Critical Path Testing Skill

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.

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.

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.

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.

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.

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.