debug

Identify and fix failing tests across multiple test suites.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly identify, isolate, and fix failing tests, reducing debugging time and preventing regressions.

Core Features & Use Cases

  • Parallel debugging: spawn parallel agents to investigate multiple failing tests at once.
  • Automated failure capture: summarize error messages, stack traces, and context to speed root-cause analysis.
  • Workflow orchestration: coordinate test runs, review changes, and push fixes.

Quick Start

Run the /debug command with the name of a failing test to begin debugging.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug failing tests in parallel across multiple test suites?

Debug failing tests in parallel by spawning parallel agents to investigate multiple test failures at once, enabling targeted fixes via agent delegation across your test suites. The skill coordinates parallel test runs and collects errors to speed root-cause analysis.

Can I use this to automatically capture error messages and stack traces from CI workflows?

Yes, you can capture error messages in CI workflows through automated failure capture, which summarizes error messages, stack traces, and context to speed root-cause analysis during your continuous integration runs.

What is the best way to coordinate test runs and push fixes for failing tests?

The best way to coordinate test runs and push fixes is through workflow orchestration, which coordinates test runs, reviews changes, and pushes fixes directly after isolating the failing tests.

How do I start debugging a specific failing test?

Start debugging a specific failing test by running the /debug command with the name of the failing test to begin the parallel debugging process and isolate the root cause.

Does this approach work for local development as well as CI workflows?

Yes, this approach works for local development as well as CI workflows, applying parallel debugging of test failures across both environments to quickly identify, isolate, and fix failing tests while preventing regressions.