stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
Profile →npx skills add opensquilla/opensquilla --skill stack-trace-go-probe --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Stack Trace Go Probe Return only: ``` LANGUAGE_PROBE: go CHECKS: - <nil pointer / error-return / goroutine boundary check> - <package or interface contract check> REPRODUCER: - <minimal go test ./... -run <Name> command or snippet> PATCH_TARGETS: - <nil guard / explicit error handling / interface assertion target> VERIFY: - <go test command> ``` Prefer narrow `go test ./path -run TestName` commands when the trace exposes a package or symbol. Do not suggest mutating production state.
What does the stack-trace-go-probe skill do?
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill stack-trace-go-probe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.