stack-trace-rust-probe

Generates Rust-specific panic checks, cargo test reproducers, and patch targets from stack traces.

6.8k|540|Updated May 6, 2026

Search Tags:#stack trace #Rust #Debugging #panic #cargo test #backtrace #Error handling

One-click install

npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-rust-probe

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: stack-trace-rust-probe
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/bundled/stack-trace-rust-probe
Command: npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-rust-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When investigating a Rust panic or backtrace, generic debugging advice misses language-specific issues like unwrap/expect misuse, Option/Result handling, and trait or lifetime boundaries. This Skill produces a focused Rust diagnostic checklist so investigators know exactly what to check, how to reproduce the failure, and where to patch.

Core Features & Use Cases

Rust-Specific Checks: Emits targeted checks for panic, unwrap, expect, Option/Result handling, plus trait, lifetime, and thread boundary concerns.
Minimal Reproducers: Suggests narrow cargo test <name> commands when the trace exposes a symbol, avoiding broad rewrites.
Patch Targets: Identifies concrete fixes such as replacing unwrap/expect, adding map_err, or propagating Results explicitly.
Use Case: As an internal helper for meta-stack-trace-investigator, it activates when a Rust panic needs structured diagnosis, returning a LANGUAGE_PROBE block with checks, a reproducer, patch targets, and a verification command.

Quick Start

Ask the agent to investigate this Rust panic backtrace and produce the Rust-specific checks, a minimal cargo test reproducer, and patch targets.

Frequently Asked Questions about stack-trace-rust-probe

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

FAQPage Schema

How do I debug a Rust panic from a backtrace?▼

Start by checking unwrap, expect, and Option/Result handling at the frames shown in the trace. Then build a minimal cargo test reproducer targeting the exposed symbol and patch the failure with explicit Result propagation or map_err.

How to reproduce a Rust panic with cargo test?▼

Use a narrow cargo test command naming the specific test or symbol exposed in the trace, such as cargo test <name>. This isolates the failure faster than running the full test suite.

What should replace unwrap and expect in Rust error handling?▼

Replace unwrap and expect with explicit Result propagation using the ? operator, or convert errors with map_err when crossing error-type boundaries. This turns panics into recoverable, typed errors.

When is this Rust probe not the right tool?▼

It is an internal helper for meta-stack-trace-investigator and is not user-invocable or model-invocable on its own. For non-Rust traces or broad refactoring needs, use the parent investigator or a different language probe.