gad:debug

Track software debugging hypotheses and traces in a persistent session file.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/B2Gdevs/custom_portfolio --skill gad-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gad:debug
Source: https://github.com/B2Gdevs/custom_portfolio/tree/main/skills/rp-debug
Command: npx skills add https://github.com/B2Gdevs/custom_portfolio --skill gad-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a structured, persistent approach to investigating build, runtime, test, and network failures by capturing investigation state in a session file so that hypotheses, traces, and steps can be resumed and shared across environments.

Core Features & Use Cases

  • Persistent session snapshots: create and update a session file that records investigation notes, command outputs, and reproduction steps for long-running or intermittent failures.
  • Investigation patterns reference: includes curated starting points for build, runtime, test, network, and silent-failure diagnoses to speed hypothesis formation.
  • Migration and CLI integration: serves as a deprecated RepoPlanner alias that points to the canonical get-anything-done/debug skill and supports CLI snapshot workflows for project triage.

Quick Start

Run the gad:debug snapshot command for your project to create a persistent investigation session file that you can annotate and resume later.

Frequently Asked Questions about gad:debug

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

FAQPage Schema
How do I debug an intermittent build failure across different workspaces?

A persistent session file records investigation notes, command outputs, and reproduction steps, allowing you to systematically debug intermittent build failures and resume the investigation later across environments.

What is the best way to triage CI failures using a persistent session file?

The best way to triage CI failures is using a persistent session file to track investigation state, applying systematic debugging to capture reproducible traces and stepwise hypotheses for long-running or intermittent failures.

How do I start a debugging investigation for a project repository?

Run the gad:debug snapshot command in your project workspace to create a persistent investigation session file, which you can then annotate and resume later for repository-level debugging.

Does this debugging approach require Node.js access to the vendor toolkit?

Yes, systematic debugging requires a project workspace with Node.js access to the vendor/get-anything-done toolkit, CLI snapshot capability, and supporting investigation reference materials to function properly.

Can I use a persistent session file for local runtime failure investigation?

Yes, persistent-session debugging applies to local runtime failure investigation by capturing investigation state in a session file so that hypotheses, traces, and steps can be resumed and shared across environments.

What investigation patterns are available for diagnosing silent failures?

Investigation patterns reference includes curated starting points for build, runtime, test, network, and silent-failure diagnoses to speed hypothesis formation during your debugging session.