godebug-verify

Verify Go runtime behavior using Delve breakpoints and the HAEC protocol.

3|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/8gears/godebug-agentic --skill godebug-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godebug-verify
Source: https://github.com/8gears/godebug-agentic/tree/main/.claude/skills/godebug-verify
Command: npx skills add https://github.com/8gears/godebug-agentic --skill godebug-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proactive runtime verification helps AI agents confirm Go code behaves as intended before marking work complete, reducing reliance on static tests and reviews.

Core Features & Use Cases

  • Proactive verification mindset for Go code, focusing on runtime validation for concurrency, error propagation, and control flow.
  • HAEC protocol (Hypothesis → Assertion → Execution → Conclusion) guiding step-by-step verification.
  • Integrated with the godebug tool to set breakpoints, inspect state, and validate outcomes for code generated by AI or manual development.

Quick Start

Start a verification session by launching your Delve-based debugger and connecting to a running process: godebug --addr $ADDR restart Set an assertion point: godebug --addr $ADDR break "sync.(*WaitGroup).Add" Continue to the assertion: godebug --addr $ADDR continue Inspect values: godebug --addr $ADDR eval "err" Decide and conclude: godebug --addr $ADDR continue Conclusion is drawn from the observed outputs; never mark code done until CONFIRMED.

Frequently Asked Questions about godebug-verify

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

FAQPage Schema
How do I verify Go concurrency and error propagation at runtime?

Runtime verification for Go code uses a Delve-based debugger to set breakpoints, inspect state, and validate concurrent behavior and error propagation before marking work complete.

What is the HAEC protocol for Go code verification?

The HAEC protocol is a step-by-step verification method: Hypothesis, Assertion, Execution, and Conclusion, guiding targeted runtime observations to draw evidence-based conclusions about Go code behavior.

How do I set assertion points to inspect state in a running Go process?

Inspect state in a running Go process by connecting a Delve-based debugger via an address, setting breakpoint assertions on target functions, and evaluating variables to validate outcomes.

Can I use this runtime verification approach for AI-assisted Go development?

Yes, proactive runtime verification is designed for AI-assisted development, confirming that generated Go code behaves as intended through targeted debugger observations rather than relying solely on static tests.

When should I not rely on static tests for Go code correctness?

Static tests fall short for concurrent code and complex control flow; runtime verification proactively confirms actual execution behavior and state inspection to ensure code correctness before completion.