debug

Automate LocusQ debugging workflows with codebase inspection and runtime diagnostics.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/joshband/LocusQ --skill debug-joshband
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/joshband/LocusQ/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/joshband/LocusQ --skill debug-joshband

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates debugging workflows for the LocusQ project by inspecting code, configuring the debugger, and collecting runtime diagnostics. Use when user reports a crash or unexpected behavior to accelerate remediation and reduce debugging cycles.

Core Features & Use Cases

  • Automated codebase analysis to identify failure points and likely root causes.
  • Automatic debugger configuration and structured runtime diagnostics collection.
  • Generated remediation guidance and repeatable diagnostic reports for QA and engineering teams.
  • Use case: when a crash occurs on startup, trigger diagnostic collection and suggested fixes.

Quick Start

Invoke the Claude Debug Skill Router to start an autonomous diagnostic session for the LocusQ project.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I automate runtime diagnostics collection for a crash report?

Automated runtime diagnostics collection works by inspecting the codebase, configuring the debugger, and gathering structured diagnostic outputs to identify failure points and likely root causes. This process accelerates remediation by providing deterministic steps and safe data collection for crash reports.

What's the best way to debug unexpected behavior in a staging environment?

Debugging unexpected behavior in staging involves triggering an autonomous diagnostic session that analyzes code, configures the debugger, and collects runtime data. This generates repeatable diagnostic reports and remediation guidance tailored for QA and engineering teams across staging environments.

How does automated codebase analysis identify root causes for performance anomalies?

Automated codebase analysis identifies root causes for performance anomalies by inspecting code to locate failure points, then configuring a debugger to collect structured runtime diagnostics. It produces deterministic diagnostic outputs that guide remediation for performance issues across development and QA environments.

Do I need to manually configure a debugger to collect diagnostic data?

No manual debugger configuration is needed. The debugging workflow automatically configures the debugger and handles argument handling and safe data collection, producing structured diagnostic outputs that guide remediation without requiring manual setup steps.

Can I use this debugging workflow across development and QA environments?

Yes, this debugging workflow supports crash reports, unexpected behavior, and performance anomalies across development, staging, and QA environments. It generates repeatable diagnostic reports and remediation guidance suitable for both engineering and QA teams.

What limitations exist when using autonomous debugging for performance anomalies?

Autonomous debugging for performance anomalies is limited to collecting structured runtime diagnostics and suggesting fixes based on deterministic codebase inspection. It does not directly patch code but provides diagnostic reports and remediation guidance for engineering teams to act upon.