debug

Coordinate a multi-agent team to debug software regressions and test fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill tackles the frustrating "it worked, now it's broken" scenario by systematically identifying and fixing regressions.

Core Features & Use Cases

  • Multi-Agent Debugging Team: Spawns specialized agents to investigate, analyze timelines, form hypotheses, and test fixes.
  • CI Integration: Checks CI failures first for PR-related issues.
  • Continuity: Maintains a .debug-log.md for ongoing sessions and detailed records.
  • Use Case: Your CI pipeline suddenly starts failing after a merge. Invoke this Skill to pinpoint the exact commit or change causing the failure and automatically test potential fixes.

Quick Start

Use the debug skill to investigate why the latest deployment is failing.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I automate debugging for software regressions in CI?

Automated regression debugging uses a multi-agent team to analyze CI failures and conversation history. It investigates current states, forms ranked hypotheses, and sequentially tests fixes to pinpoint the exact root cause of broken deployments.

Can I use a multi-agent team to find the root cause of a broken deployment?

Yes, a multi-agent debugging team coordinates specialized agents to investigate timeline changes and analyze conversation history. This systematic approach identifies the specific commit or change causing the broken deployment.

How do I troubleshoot CI failures by analyzing timeline changes?

Troubleshooting CI failures involves analyzing timeline changes to form ranked hypotheses. Specialized agents investigate the current state and check CI failures first, testing potential fixes sequentially to resolve the regression.

Does systematic debugging support continuous debugging sessions?

Systematic debugging supports continuous debugging sessions by maintaining a persistent `.debug-log.md` file. This log preserves detailed records of ongoing investigations, allowing you to pause and resume troubleshooting regressions seamlessly.

What is the best way to identify root causes after a merge breaks my pipeline?

The best way to identify root causes after a merge breaks your pipeline is to spawn specialized agents that check CI failures and analyze timeline changes. They form ranked hypotheses and test fixes sequentially to resolve the regression.

Are there limitations to using agents for regression troubleshooting?

A limitation of using agents for regression troubleshooting is the dependency on analyzing conversation history and CI logs. If CI failures are not properly logged or timeline changes are ambiguous, forming accurate ranked hypotheses becomes significantly harder.