bugfix-and-debug

Diagnose errors and failing tests in Laravel and React applications.

Updated Dec 22, 2025
One-click install
npx skills add https://github.com/htooayelwinict/claude-config --skill bugfix-and-debug-htooayelwinict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix-and-debug
Source: https://github.com/htooayelwinict/claude-config/tree/main/skills/bugfix-and-debug
Command: npx skills add https://github.com/htooayelwinict/claude-config --skill bugfix-and-debug-htooayelwinict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides debugging and bug-fixing across Laravel + React apps with structured phases and verification steps.

Core Features & Use Cases

  • Evidence collection, hypothesis formation, and minimal fixes.
  • Regression testing and verification templates.
  • Clear output templates for documenting fixes.

Quick Start

Collect evidence for a failing test, hypothesize root causes, apply a minimal fix, and verify with tests.

Frequently Asked Questions about bugfix-and-debug

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

FAQPage Schema
How do I debug failing tests in Laravel and React applications?

Debugging failing tests involves collecting evidence from error messages and stack traces, forming hypotheses about root causes, applying minimal fixes, and verifying with composer test and npm run tests. This Skill guides you through structured diagnosis across both Laravel backend and React frontend environments.

What's the best way to diagnose a 500 error or TypeError in a Laravel + React app?

Diagnose errors by running mandatory verification commands (composer test, npm run types, npm run lint), examining stack traces to identify failure points, hypothesizing root causes, and applying targeted fixes. The Skill provides structured templates to document findings and validate fixes.

How do I fix bugs while ensuring I don't introduce regressions?

Fix bugs by following a verification loop: collect evidence, form hypotheses, apply a minimal fix, then run regression tests. This Skill emphasizes verification templates and structured bugfix reports to confirm your fix doesn't break existing functionality.

Can I use this debugging approach with Pest and Vitest tests?

Yes. This Skill applies to failing Pest tests in Laravel and Vitest tests in React, handling exceptions, TypeErrors, and unexpected behavior across both test frameworks.

What should I do after identifying and fixing a bug?

After applying a fix, verify it by running composer test, npm run types, and npm run lint, then output a structured bugfix report documenting the issue, root cause, fix applied, and verification results.