{"enrichment":{"faq":[{"a":"laravel-systematic-debugging guides you through a four-phase methodology that eliminates guesswork. Start by gathering context\u2014check logs, inspect Laravel Telescope, and trace data flow. Then isolate the problem by comparing expected vs. actual behavior and forming testable hypotheses. Before applying any fix, create a failing test to verify the issue exists. Finally, implement your fix and confirm tests pass without breaking other code. This approach avoids quick patches that mask symptoms rather than solving root causes.","q":"How to debug Laravel applications systematically?"},{"a":"laravel-systematic-debugging enforces a structured four-phase process: (1) Gather\u2014collect logs, use Telescope to inspect queries and requests, trace data flow through your code; (2) Isolate\u2014compare what you expected vs. what actually happened, form specific hypotheses; (3) Test\u2014write a failing test that reproduces the bug before fixing anything; (4) Fix & Verify\u2014implement your solution and confirm all tests pass. This prevents symptom-masking patches and ensures fixes address actual problems, not just surface errors.","q":"What's the laravel-systematic-debugging process for root cause investigation?"},{"a":"laravel-systematic-debugging teaches you to avoid random fixes by following Laravel conventions and testing hypotheses first. When a test fails, don't guess\u2014gather evidence using logs and Telescope, isolate the root cause by comparing expected behavior to actual behavior, then write a test that reproduces the bug. Only after your test fails should you implement a fix. Verify that your fix makes the test pass and doesn't break other tests. This test-driven approach ensures you're solving the real problem, not just making the error go away.","q":"How do I fix Laravel test failures and bugs properly?"},{"a":"laravel-systematic-debugging covers Eloquent debugging through structured tracing: use Laravel Telescope to inspect queries and spot N+1 problems, enable query logging to see actual SQL, and use Tinker to test relationships interactively. Trace data flow from your controller through models to understand where queries execute. Form hypotheses about missing eager loads or incorrect relationships, then write tests to verify. This prevents lazy-loading surprises and ensures your queries are optimized before deployment.","q":"What laravel-systematic-debugging techniques help with Eloquent query debugging?"},{"a":"laravel-systematic-debugging emphasizes Laravel Telescope as a core investigation tool. Telescope captures requests, queries, logs, and exceptions in real time. Use it to inspect Eloquent queries and spot N+1 problems, trace request flow through your application, and review error context. When debugging, open Telescope, reproduce the issue, then examine the captured data\u2014queries show you what's actually running, request tabs show middleware and controller execution, and logs reveal application state. This structured inspection replaces guesswork with concrete evidence.","q":"How to use Laravel Telescope for debugging?"},{"a":"laravel-systematic-debugging prevents the trap of symptom-masking patches that create new problems. Quick fixes often hide root causes\u2014you silence an error without understanding why it occurred, then face cascading failures later. The systematic approach enforces root cause investigation first: gather evidence, isolate the actual problem, test your hypothesis, then implement a fix. By creating failing tests before fixing, you ensure your solution addresses the real issue and doesn't break other code. This takes slightly longer upfront but saves debugging time and prevents production surprises.","q":"Why should I avoid quick fixes and follow laravel-systematic-debugging instead?"}],"shadow_tags":["root-cause-analysis","systematic-troubleshooting","hypothesis-testing","query-optimization","framework-conventions","error-investigation","debugging-workflow","code-tracing"],"summary_rewrite":"This skill guides you through a four-phase debugging methodology designed to eliminate guesswork when troubleshooting Laravel issues. By enforcing root cause investigation before any fix attempt, it helps you avoid symptom-masking patches that create new problems. The process covers log analysis, Laravel Telescope inspection, data flow tracing, pattern comparison, hypothesis testing, and test-driven implementation."},"files":[{"bytes":11178,"path":"skills/laravel-systematic-debugging/SKILL.md","sha256":"e7a744a919be2844b95b1b80fb27200ae8b430315f722afbf1a7b3a01020e72c","url":"https://skillfed.io/files/iSerter/laravel-claude-agents/laravel-systematic-debugging/594ca717/SKILL.md"}],"id":"iSerter/laravel-claude-agents/laravel-systematic-debugging","links":{"html":"https://skillfed.io/iSerter/laravel-claude-agents/laravel-systematic-debugging","md":"https://skillfed.io/iSerter/laravel-claude-agents/laravel-systematic-debugging.md","repo":"https://github.com/iSerter/laravel-claude-agents"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":8,"language":"PHP","last_updated":"2026-04-19","license":"MIT","name":"laravel-systematic-debugging","publisher":"iSerter","stars":41},"relations":{"similar":[{"id":"rawveg/skillsforge-marketplace/laravel"},{"id":"Jeffallan/claude-skills/laravel-specialist"},{"id":"iSerter/laravel-claude-agents/eloquent-best-practices"},{"id":"AsyrafHussin/agent-skills/laravel-best-practices"},{"id":"Pixel-Process-UG/superkit-agents/laravel-specialist"},{"id":"elementalsouls/Claude-BugHunter/hunt-laravel"},{"id":"iSerter/laravel-claude-agents/laravel-tdd"},{"id":"affaan-m/ECC/laravel-security"},{"id":"personamanagmentlayer/pcl/php-expert"},{"id":"JustSteveKing/laravel-api-skill/laravel-api"}]},"slug":{"owner":"iSerter","repo":"laravel-claude-agents","skill":"laravel-systematic-debugging"},"version":"594ca717"}