code-review-test-analyzer

Analyze code changes to identify critical gaps in test coverage.

21|8|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/speednet-software/speedwave --skill code-review-test-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-test-analyzer
Source: https://github.com/speednet-software/speedwave/tree/main/.claude/skills/code-review-test-analyzer
Command: npx skills add https://github.com/speednet-software/speedwave --skill code-review-test-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams assess code changes to ensure critical paths are sufficiently tested, preventing regressions from slipping through.

Core Features & Use Cases

  • Analyze test coverage quality across diffs to identify untested error paths and edge cases.
  • Evaluate tests for behavior-focused coverage rather than line-count dominance, with actionable recommendations.
  • Use Case: When reviewing a PR, generate a prioritized list of new tests and test-coverage improvements aligned with critical business logic.

Quick Start

Review the latest git diff and return a prioritized list of test improvements and added cases

Frequently Asked Questions about code-review-test-analyzer

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

FAQPage Schema
How do I find untested edge cases in a git diff during code review?

To find untested edge cases in a git diff, analyze the code changes to surface untested error paths and prioritize gaps by impact, generating a prioritized list of concrete test additions with rationale.

What is behavior-focused test coverage and how does it differ from line-count coverage?

Behavior-focused test coverage evaluates tests for behavioral correctness and critical business logic rather than line-count dominance, providing actionable recommendations to ensure critical paths are sufficiently tested.

How do I generate a prioritized list of test improvements for a pull request?

Generate a prioritized list of test improvements for a pull request by analyzing the feature branch diff to identify critical test gaps and suggesting concrete test additions aligned with critical business logic.

Can I use diff analysis to prevent regression testing failures in feature branches?

Yes, you can use diff analysis on feature branches to assess code changes, identify critical gaps in test coverage, and prevent regressions from slipping through untested error paths.

Does test coverage analysis work without integrating external testing frameworks?

Test coverage analysis evaluates the behavioral correctness of existing tests directly from code changes without requiring external testing framework integrations, focusing on surfacing untested error paths and edge cases.