stack-trace-go-probe

Name: stack-trace-go-probe
Availability: InStock
Author: opensquilla

Generates Go-specific nil checks, test reproducers, and patch targets from panic stack traces.

6.8k|540|Updated May 6, 2026

Search Tags:#stack trace #go test #Debugging #panic #GO #Error handling #nil pointer

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When investigating a Go panic or stack trace, engineers need a consistent checklist of Go-specific checks, a minimal test reproducer, and clear patch targets instead of ad-hoc debugging notes.

Core Features & Use Cases

Go-Specific Checks: Produces nil pointer, error-return, goroutine boundary, and interface contract checks tailored to the trace.
Minimal Reproducers: Suggests narrow go test ./path -run TestName commands when the trace exposes a package or symbol.
Patch Targets: Identifies nil guards, explicit error handling, and interface assertion targets, plus a verification test command.
Use Case: As an internal helper for meta-stack-trace-investigator, it structures the Go portion of a crash investigation into a fixed LANGUAGE_PROBE output format.

Quick Start

Ask the agent to investigate a Go panic stack trace and it will return the structured probe with checks, a reproducer, patch targets, and a verify command.

Frequently Asked Questions about stack-trace-go-probe

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

FAQPage Schema

How do I debug a Go panic stack trace?▼

Start by identifying the package and symbol in the trace, then check for nil pointer dereferences, unhandled error returns, and goroutine boundary issues. Reproduce the failure with a narrow go test ./path -run TestName command before patching.

How to reproduce a Go panic with go test?▼

Write a minimal test targeting the failing function and run it with go test ./path -run TestName. Narrow test commands isolate the failing package or symbol exposed in the stack trace.

What causes nil pointer dereference panics in Go?▼

Nil pointer dereferences occur when code accesses fields or methods on a nil pointer, often from unchecked error returns or missing nil guards. Adding explicit nil checks and error handling at the identified patch targets prevents them.

Can this probe modify production code or state?▼

No. The probe only returns checks, reproducer commands, patch targets, and verification commands as text. It explicitly avoids suggesting any mutation of production state.

When should I use narrow go test commands instead of go test ./...?▼

Use narrow go test ./path -run TestName commands when the stack trace exposes a specific package or symbol. This isolates the failure faster and avoids running unrelated tests during reproduction.