debug-pro

Diagnose code defects and runtime errors from crash logs and test failures.

Updated May 17, 2026
One-click install
npx skills add https://github.com/tiankong0101-byte/skills-registry --skill debug-pro-tiankong0101-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-pro
Source: https://github.com/tiankong0101-byte/skills-registry/tree/main/skills/debug-pro
Command: npx skills add https://github.com/tiankong0101-byte/skills-registry --skill debug-pro-tiankong0101-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose code defects, runtime errors, failing tests, and quality issues so you can quickly identify what broke and how to fix it.

Core Features & Use Cases

  • Issue Diagnosis: Trace crashes, stack traces, lint errors, and type failures back to the root cause.
  • Minimal Bug Fixes: Apply focused code changes that resolve the defect without unnecessary scope creep.
  • Verification Workflow: Confirm the repair through testing, linting, and type-checking before closing the issue.
  • Use Case: A CI pipeline starts failing after a recent change; use this Skill to pinpoint the regression, patch it, and verify the fix.

Quick Start

Use the debug-pro skill to investigate this error log, identify the root cause in the codebase, apply the smallest safe fix, and verify the result with tests.

Frequently Asked Questions about debug-pro

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

FAQPage Schema
How do I find the root cause of a runtime error from a stack trace?

To find the root cause of a runtime error, inspect the stack trace to locate the failing code, examine the source for defects, and trace the crash back to its origin. Apply minimal corrective edits to resolve the defect without unnecessary scope creep.

What is the best way to fix failing tests after a CI pipeline regression?

The best way to fix failing tests from a CI pipeline regression is to pinpoint the broken code change, apply a focused and minimal patch to resolve the defect, and verify the repair through testing, linting, and type-checking.

Can I use code review findings to diagnose and fix software defects?

Yes, code review findings can diagnose software defects. Inspect the flagged source precisely, apply minimal bug fixes to resolve the quality issue, and validate the corrective edit through tests and linting before closing the issue.

How do I verify a bug fix is safe before merging code changes?

To verify a bug fix is safe before merging, run a validation workflow that confirms the repair through testing, linting, and type-checking. This ensures the minimal corrective edit resolves the defect without introducing new failures.

Why does my code crash when I apply a patch, and how do I safely fix it?

Code crashes after a patch often stem from unresolved root causes. Safely fix it by diagnosing the runtime error precisely, applying the smallest corrective edit to resolve the defect, and validating the result with tests.