closed-loop-debug

Automates bug identification, debugging, rebuilding and verification for nostr GTK4 apps via Broadway UI.

8|2|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/chebizarro/nostrc --skill closed-loop-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: closed-loop-debug
Source: https://github.com/chebizarro/nostrc/tree/main/skills/closed-loop-debug
Command: npx skills add https://github.com/chebizarro/nostrc --skill closed-loop-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a fully automated, deterministic workflow for identifying, reproducing, diagnosing, fixing, and verifying bugs in GTK4 applications within the nostr stack, eliminating the need for human intervention between iterations.

Core Features & Use Cases

  • Automated Bug Lifecycle: Manages the entire bug resolution process from identification to verification.
  • Tool Integration: Seamlessly integrates debugging tools like GDB/LLDB, sanitizers (ASan), and UI testing frameworks (Broadway/Playwright).
  • Use Case: An LLM agent can use this Skill to automatically detect a crash in the gnostr application, pinpoint the exact line of faulty code using GDB and ASan, apply a fix, rebuild the application, and confirm the fix using the Broadway UI, all without human input.

Quick Start

Use the closed-loop-debug skill to find and fix the bug reported in the latest test run.

Frequently Asked Questions about closed-loop-debug

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

FAQPage Schema
How do I automate GTK application debugging with GDB and an LLM agent?▼

Automated GTK application debugging uses a closed-loop workflow that integrates GDB and LLM agents to identify bugs, execute tests, apply code fixes, rebuild, and verify results via Broadway UI without human intervention.

What is closed-loop debugging for GTK4 applications?▼

Closed-loop debugging for GTK4 applications is a deterministic workflow that automates the entire bug lifecycle from identification and reproduction to diagnosis, fixing, rebuilding, and verifying using sanitizers and Broadway UI testing.

How do I fix GTK app crashes automatically using AddressSanitizer?▼

To fix GTK app crashes automatically, an LLM agent uses AddressSanitizer to detect the crash, GDB to pinpoint the faulty code line, applies a fix, rebuilds the application, and confirms the resolution using the Broadway UI.

Can I use Broadway and GDB together for automated UI testing?▼

Yes, Broadway and GDB integrate seamlessly within an automated debugging methodology to execute UI testing, pinpoint exact faulty code lines, and verify application fixes deterministically.

Does closed-loop debugging work with nostr GTK applications?▼

Closed-loop debugging is specifically designed for nostr GTK applications, providing a fully automated workflow that manages bug identification, test execution, debugging, and verification without requiring manual input between iterations.

What are the limitations of automated debugging for GTK apps?▼

Automated debugging for GTK apps requires a deterministic methodology integrating GDB, sanitizers, and Broadway UI, relying on seamless tool integration to eliminate human intervention between bug identification and verification iterations.