lc:analyze-error

Analyze Laravel stack traces and apply code fixes across controllers, models, and database layers.

12|2|Updated Apr 8, 2026

Search Tags:#debugging #refactoring #php #laravel #error-analysis #stacktrace

Ready to run

npx skills add https://github.com/edulazaro/laraclaude --skill lc-analyze-error

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lc:analyze-error
Source: https://github.com/edulazaro/laraclaude/tree/main/skills/analyze-error
Command: npx skills add https://github.com/edulazaro/laraclaude --skill lc-analyze-error

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the time-consuming process of manually debugging Laravel stack traces by automatically identifying the root cause and providing precise, actionable code fixes.

Core Features & Use Cases

Automated Root Cause Analysis: Parses complex stack traces, SQL errors, and framework exceptions to explain exactly why a failure occurred.
Context-Aware Remediation: Reads relevant source files, migrations, and models to suggest specific code changes that resolve the issue.
Safe Application: Offers dry-run modes and confirmation prompts to ensure fixes are applied safely without unintended side effects.

Quick Start

Invoke the analyze-error skill and paste your Laravel stack trace to receive a detailed diagnosis and a proposed code fix.

Frequently Asked Questions about lc:analyze-error

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

FAQPage Schema

How do I diagnose a Laravel stack trace to find the root cause of an exception?▼

To diagnose a Laravel stack trace, you parse the error logs and framework exceptions to identify the root cause. Automated analysis reads relevant source files, migrations, and models to pinpoint exactly why the failure occurred across controllers and database layers.

What is the best way to fix Laravel SQL errors and logic failures automatically?▼

Fixing Laravel SQL errors and logic failures automatically involves analyzing the stack trace and generating precise code changes. Context-aware remediation reads project source files to apply targeted patches across application models and controllers.

Can I apply automated code fixes to Laravel source files without causing unintended side effects?▼

Yes, you can apply automated code fixes safely by using dry-run modes and confirmation prompts. This ensures that proposed patches for controllers and models are reviewed before being written to project source files, preventing unintended side effects.

Does automated Laravel error analysis require read and write access to project source files?▼

Yes, automated Laravel error analysis requires read and write access to project source files. This access is necessary to perform diagnostic analysis on stack traces and apply the generated code fixes directly to application controllers, models, and migrations.

What types of Laravel errors can be resolved by analyzing stack traces and error logs?▼

Analyzing Laravel stack traces and error logs can resolve exceptions, syntax errors, and logic failures. This diagnostic process operates across application controllers, models, and database layers to identify the root cause and generate precise fixes.