skills.rest
fyodoriv
fyodorivCOMMUNITY
Explore all skills by this author →
GitHub

manual-debug

Automate guided debugging workflows with structured checklists for local software failures.

Updated Aug 27, 2026
Search Tags:#debugging#troubleshooting#diagnostics#software#development-workflow#manual-debug
One-click install
npx skills add https://github.com/fyodoriv/agentbrew --skill manual-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-debug
Source: https://github.com/fyodoriv/agentbrew/tree/main/real-e2e/fixtures/us07-us17-source-and-existing-setup/home/.claude/skills/manual-debug
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill manual-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual debugging can be time-consuming and error-prone. This skill provides a structured approach to reproduce, diagnose, and fix issues in a local development environment.

Core Features & Use Cases

  • Step-by-step debugging checklists to systematically collect logs, reproduce failures, and verify fixes.
  • Guidance for common failure modes in software development, including runtime errors, build failures, and flaky tests.
  • Use Case: A developer encounters a failing unit test; follow the checklist to reproduce, locate root cause, implement a fix, and re-run tests.

Quick Start

Reproduce a failing scenario in your local project, follow the guided steps, and validate the fix by re-running the relevant tests.

Frequently Asked Questions about manual-debug

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

FAQPage Schema
What is guided manual debugging for local software failures?▼

Guided manual debugging is a structured approach to reproduce, diagnose, and fix issues in a local development environment. It uses step-by-step checklists to systematically collect logs, reproduce failures, and verify fixes.

How do I debug a failing unit test systematically?▼

To debug a failing unit test, follow a step-by-step debugging checklist to reproduce the failing scenario, locate the root cause, implement a fix, and validate the results by re-running the relevant tests.

Can structured troubleshooting help diagnose runtime errors and flaky tests?▼

Structured troubleshooting provides guidance for common failure modes including runtime errors, build failures, and flaky tests. It ensures a clear debugging process with verifiable fixes through structured checkpoints.

What is the best way to reproduce and verify fixes for local codebase issues?▼

The best way to fix codebase issues is using a structured manual debugging workflow. Reproduce the failing scenario in your local project, follow the guided diagnostic steps, and validate the fix by re-running tests.

Do I need specific dependencies to use a manual debugging checklist?▼

No specific dependencies are required to use a manual debugging checklist. The process applies to general development and testing scenarios where reproducible steps and logs diagnose issues across codebases.

Why should I use a structured debugging workflow instead of ad hoc troubleshooting?▼

Ad hoc troubleshooting can be time-consuming and error-prone. A structured debugging workflow provides systematic steps and checkpoints to collect logs, reproduce failures, and ensure verifiable fixes.

Related Skills

Explore More Software Engineering Skills→
JuanTaco4YouJuanTaco4You

debug-repro-fix-regression-test

Reproduce incidents from logs into deterministic regression tests.

Community
Basic
bennybennisonbennybennison

debugging-methodology

Diagnose software bugs through reproduction, isolation, hypothesis testing, and regression verification.

Community
Intermediate
SimHackerSimHacker
49

debugging

Systematically debug issues by hypothesizing, testing, and tracking evidence.

Community
Advanced
T1nker-1220T1nker-1220

debugging-systematic

Diagnose software issues through root-cause analysis with hypotheses and logging.

Community
Intermediate