Debugging and Troubleshooting

Diagnose Rust compile errors, test failures, and runtime panics with cargo commands.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/hiromima/collaborative-canvas --skill debugging-and-troubleshooting-hiromima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Debugging and Troubleshooting
Source: https://github.com/hiromima/collaborative-canvas/tree/main/.claude/skills/debugging-troubleshooting
Command: npx skills add https://github.com/hiromima/collaborative-canvas --skill debugging-and-troubleshooting-hiromima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic error diagnosis and debugging workflow for Rust code. Use when code isn't working, tests fail, or runtime errors occur.

Core Features & Use Cases

  • Workflows for diagnosing compile errors, test failures, and runtime panics in Rust projects.
  • Provides commands and patterns for classification, diagnostics, and fixes.
  • Use Case: When a Rust project fails to compile or tests fail, follow structured steps to identify root cause and proposed remedies.

Quick Start

Describe your Rust project issue to begin a guided debugging workflow.

Frequently Asked Questions about Debugging and Troubleshooting

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

FAQPage Schema
How do I debug Rust compile errors systematically?▼

Debug Rust compile errors by running cargo check to isolate diagnostics, classifying the error type, and following structured root-cause analysis steps to generate actionable code fixes.

What is the best way to diagnose Rust runtime panics?▼

Diagnose Rust runtime panics by capturing proper backtraces to identify the exact failure origin, then applying a structured workflow to trace the root cause and implement the necessary fix.

How do I troubleshoot failing Rust tests with cargo test?▼

Troubleshoot failing Rust tests by running cargo test to capture failure details, classifying the test failure pattern, and following guided root-cause analysis to propose targeted remedies.

Can I use this debugging workflow for large Rust projects?▼

Yes, this systematic debugging workflow explicitly scales across typical Rust projects from small to large, diagnosing compile errors, test failures, and runtime panics regardless of project size.

Why do I need cargo check and backtraces for Rust diagnostics?▼

Cargo check and backtraces provide the essential diagnostic data required to produce actionable insights, allowing the workflow to accurately classify errors and guide root-cause analysis.