laravel-debug

Diagnose Laravel issues by gathering logs, creating reproduction tests, and verifying fixes.

1|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/bmadigan/ask-my-doc --skill laravel-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: laravel-debug
Source: https://github.com/bmadigan/ask-my-doc/tree/main/.claude/skills/laravel-debug
Command: npx skills add https://github.com/bmadigan/ask-my-doc --skill laravel-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel debugging is often ad-hoc and time-consuming. This Skill provides a structured workflow to diagnose and resolve Laravel application issues by collecting browser and server logs, error details, and runtime context to guide fixes.

Core Features & Use Cases

  • Systematic debugging workflow: Collect browser and Laravel logs, identify root causes, and plan fixes.
  • Guided reproduction & testing: Create focused tests to reproduce bugs and verify fixes.
  • Common pattern guidance: Address issues such as Vite/asset errors, N+1 queries, validation, authorization, and CSRF-related failures.
  • Practical use case: When a Laravel app shows a 500 error after a deployment, follow this skill to gather diagnostics and implement a minimal repro and fix.

Quick Start

Follow the debugging workflow to begin diagnosing a Laravel issue: gather logs, reproduce the issue with a focused test, apply a fix, and verify with tests. If you modify code, run the formatter (pint) to ensure style guidelines are met.

Frequently Asked Questions about laravel-debug

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

FAQPage Schema
What is the best way to debug a Laravel 500 error after a deployment?▼

Debugging a Laravel 500 error involves collecting browser and Laravel logs, identifying the root cause, creating a focused reproduction test, applying a fix, and verifying the solution with tests.

How do I systematically resolve N+1 query issues in Laravel?▼

To resolve Laravel N+1 query issues, gather runtime context and logs to identify the performance bottleneck, then create a focused test to reproduce the query pattern before applying and verifying your optimization fix.

Can I use this workflow to troubleshoot Vite and asset compilation failures in Laravel?▼

Yes, this workflow supports troubleshooting common Laravel failure patterns including Vite and asset errors by collecting relevant browser logs and error details to guide you from issue discovery to a verified resolution.

Do I need to create reproduction tests when diagnosing Laravel application issues?▼

Yes, creating focused tests to reproduce bugs is a required step in this debugging workflow, ensuring that the identified root cause is accurate and that the applied fix is verified before completion.

How do I fix CSRF-related validation and authorization failures in Laravel?▼

Fixing CSRF-related and authorization failures requires collecting error details and logs, reproducing the validation issue with a test, and applying a structured fix to resolve the request failure pattern.

What should I do after applying a code fix during Laravel debugging?▼

After applying a code fix during Laravel debugging, you should verify the resolution with tests and run the Pint formatter to ensure your modified code meets the required style guidelines.