skills.rest
SavigeSystemZ
SavigeSystemZOFFICIAL
Explore all skills by this author →
GitHub

debug-playbook

Reproduces, isolates, and resolves failures in build, test, run-time, packaging, or install workflows.

Updated Aug 23, 2026
Search Tags:#debugging#environment#regression#root-cause#ci#bug-triage#build-failure
One-click install
npx skills add https://github.com/SavigeSystemZ/LuxeLogic --skill debug-playbook
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-playbook
Source: https://github.com/SavigeSystemZ/LuxeLogic/tree/main/database/.cursor/skills/debug-playbook
Command: npx skills add https://github.com/SavigeSystemZ/LuxeLogic --skill debug-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce, isolate, and resolve failures in builds, tests, runtimes, packaging, or installations.

Core Features & Use Cases

  • Reproduce exact failures by capturing the full error output and environment details.
  • Narrow the failing surface by isolating the trigger (e.g., a specific test, file, or step) and validating hypotheses.
  • Form a testable hypothesis and implement the smallest correct fix with clear rollback steps.
  • Add regression coverage to prevent reoccurrence and strengthen the debugging workflow.

Quick Start

Run the exact failing command, capture the full error output, and note the environment details.

Frequently Asked Questions about debug-playbook

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

FAQPage Schema
How do I isolate a root-cause bug from a failing CI pipeline?▼

To isolate a root-cause bug, reproduce the exact failure by capturing full error output and environment details, then narrow the failing surface by validating hypotheses against specific triggers like a test or build step.

What's the best way to reproduce a build failure locally?▼

The best way to reproduce a build failure is to run the exact failing command, capture the complete error output, and document the local environment details to match the staging or CI conditions.

How do I fix a test regression without breaking existing workflows?▼

Fix a test regression by forming a testable hypothesis and implementing the smallest correct fix with clear rollback steps, ensuring existing workflows remain intact while resolving the specific failure.

Does deterministic debugging work for packaging and install workflows?▼

Yes, deterministic debugging works for packaging and install workflows by reproducing exact failures, isolating the trigger step, and applying a targeted fix with regression coverage to prevent reoccurrence.

What environment details do I need to debug a runtime failure?▼

Debugging a runtime failure requires complete error logs, environment details, and a plan to confirm the fix, ensuring you can accurately reproduce the issue and validate your regression coverage.

Why should I add regression coverage after resolving a bug triage?▼

Adding regression coverage after bug triage prevents reoccurrence of the resolved failure and strengthens the debugging workflow by ensuring the smallest correct fix is validated against future changes.

Related Skills

Explore More Software Engineering Skills→
mediar-aimediar-ai
1.6k

Terminator Issue Reporter

Generate structured GitHub issues for Terminator failures with logs and reproduction steps.

Official
Advanced
moberghrmoberghr
6

debugging-and-error-recovery

Reproduce failures, localize root causes, and verify fixes with builds and tests.

Official
Advanced
ncaqncaq
3

nix-fast-build

Parallelize Nix evaluation and builds using nix-eval-jobs and nix-output-monitor.

Community
Intermediate
alti3alti3
7

litestar-debugging

Diagnose runtime issues in Litestar services using reproducible failure scenarios.

Community
Advanced