debug-tests

Diagnose failing cargo tests in Rust projects from failure localization to fix validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cychen2021/claude-skills --skill debug-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-tests
Source: https://github.com/cychen2021/claude-skills/tree/main/debug-tests
Command: npx skills add https://github.com/cychen2021/claude-skills --skill debug-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug and fix failing unit tests in Rust projects by guiding you through locating failures, reasoning about root causes, and applying minimal fixes one at a time.

Core Features & Use Cases

  • Guided failure analysis: Locate the failing test, identify the module, and inspect the assertion to determine the failure path.
  • Systematic root-cause reasoning: Trace the divergence from parser to semantic analysis and type checks, and decide whether to adjust tests or code.
  • Verified fixes: Implement minimal changes, re-run cargo test, and report which tests were fixed and why.

Quick Start

Read the cargo test output, locate the failure details, reason about the root cause using the guide, apply a minimal fix, and re-run cargo test.

Frequently Asked Questions about debug-tests

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

FAQPage Schema
How do I debug failing cargo tests in a Rust project?

Diagnosing failing cargo tests involves locating the failing assertion, reasoning about the root cause across parsing and type checks, implementing a minimal fix, and re-running cargo test to verify the failure is resolved.

What is the best way to perform root-cause analysis on a failing Rust unit test?

Root-cause analysis for a failing Rust unit test involves tracing the divergence from the parser to semantic analysis and type checks, then deciding whether to adjust the test or the underlying code.

How do I troubleshoot Rust unit test failures across semantic analysis and type checks?

Troubleshooting Rust unit test failures requires inspecting the assertion to determine the failure path, tracing the divergence through semantic analysis and type checks, and applying a minimal code or test adjustment.

Can I use a guided workflow to fix Rust unit test failures one at a time?

Yes, you can use a disciplined workflow to fix Rust unit test failures one at a time by locating the failure, reasoning about the root cause, implementing a minimal fix, and re-running cargo test for validation.

Why does my cargo test fail during semantic analysis or type checks in Rust?

Your cargo test fails during semantic analysis or type checks due to a divergence in the code path, which requires tracing the failure from the parser through to the type checks to identify the root cause.