meta-stack-trace-investigator

Orchestrates multi-source investigation of stack traces into ranked root-cause reports.

6.8k|540|Updated May 6, 2026
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill meta-stack-trace-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-stack-trace-investigator
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/exp/meta-stack-trace-investigator
Command: npx skills add https://github.com/opensquilla/opensquilla --skill meta-stack-trace-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging a pasted stack trace usually requires manually parsing the traceback, searching the repository, checking git history and issues, and guessing at root causes. This Skill automates that entire investigation workflow and produces a structured diagnosis report with ranked hypotheses and verification commands.

Core Features & Use Cases

  • Parallel Evidence Gathering: Runs repository grep, GitHub issue search, git history, diff context, memory recall, and language-specific probes concurrently after parsing the trace once.
  • Language-Aware Routing: Classifies Python, JavaScript, TypeScript, Go, or Rust traces and routes to a language-specific probe for idiomatic checks and reproducer shapes.
  • Graceful Degradation: Every evidence step has a degraded fallback, so the final report still delivers trace-contract analysis, exact search commands, and patch direction when repository access is unavailable.
  • Use Case: Paste a Python KeyError traceback from a tool-result parser and receive a report with exception semantics, a ranked root-cause matrix, reproduction snippets, patch targets, and read-only verification commands.

Quick Start

Paste your traceback into the chat and ask the agent to investigate this stack trace and find the root cause.

Frequently Asked Questions about meta-stack-trace-investigator

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

FAQPage Schema
How do I find the root cause of a Python KeyError traceback?

Paste the traceback and trigger the investigation; the Skill parses the exception class, failing file and line, and top frames, then searches the repository, git history, and issues in parallel. It returns a ranked root-cause matrix with falsifying checks and patch directions.

What languages does stack trace analysis support?

The Skill classifies traces as Python, JavaScript, TypeScript, Go, Rust, or unknown, then routes to a language-specific probe for idiomatic checks and minimal reproducer shapes. Unknown languages fall back to a generic probe.

Can I investigate a stack trace without repository access?

Yes. When repository search, git history, or issue lookups fail, the Skill labels that evidence as degraded and continues with trace-contract analysis, providing exact rg, git log, and test commands to run in the target repository.

Why does the report reject some payload shapes for a KeyError?

The exception-semantics guard reasons about what the exception class proves: for json.loads(raw)['result'] raising KeyError, the payload decoded as a dict missing that key. List, string, or null payloads would raise TypeError or JSONDecodeError instead, so they are ranked as rejected shapes.

Does the investigation modify files or run destructive commands?

No. Verification commands are restricted to read-only searches, history checks, and existing test commands. Reproducer code is provided as inline snippets to copy into existing test files, never as file-creation commands.