debug-using-debugbar

Diagnose slow requests, N+1 queries, and exceptions in Laravel via Debugbar Artisan commands.

1|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/karuhun-developer/ecommerce --skill debug-using-debugbar-karuhun-developer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-using-debugbar
Source: https://github.com/karuhun-developer/ecommerce/tree/main/.cursor/skills/debug-using-debugbar
Command: npx skills add https://github.com/karuhun-developer/ecommerce --skill debug-using-debugbar-karuhun-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fruitcake/laravel-debugbar.

What problem does it solve? Debugging Laravel applications often means guessing why a page is slow, why queries duplicate, or what caused an exception on a past request. This Skill turns Laravel Debugbar's captured request data into an inspectable CLI workflow so you can find and fix performance and error issues without manual instrumentation. ## Core Features & Use Cases - Request Discovery: List recent requests and filter by URI, HTTP method, or issue flags such as exceptions, slow queries, and high query counts. - Collector Inspection: Drill into specific Debugbar collectors (exceptions, queries, time, auth, cache) for any captured request. - Query Analysis: Detect duplicate queries signaling N+1 problems, view backtraces per statement, and run EXPLAIN or re-execute SELECT queries. - Use Case: A product page loads in 3 seconds. Run php artisan debugbar:find --issues to locate the slow request, then php artisan debugbar:queries {id} to find 40 duplicate queries, and use --statement=N to trace the N+1 back to a missing eager load in the controller. ## Quick Start Ask the AI to find recent slow or failing requests with debugbar:find --issues and analyze the queries and exceptions for the worst one.

Frequently Asked Questions about debug-using-debugbar

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

FAQPage Schema
How do I find slow requests in a Laravel application?▼

Run php artisan debugbar:find --issues to list captured requests flagged for slow duration, high query counts, or errors. Adjust thresholds with --min-duration and --min-queries, then inspect a specific request with php artisan debugbar:get {id}.

How to detect N+1 queries in Laravel using Debugbar?▼

Run php artisan debugbar:queries {id} to see duplicate query groups, which are a strong N+1 signal. Use --statement=N to get the backtrace for a specific query and trace it back to the source code missing an eager load.

Does this debugging workflow require any Laravel packages?▼

Yes, it requires fruitcake/laravel-debugbar installed in the Laravel application with debug mode enabled. The Artisan commands debugbar:find, debugbar:get, and debugbar:queries read data captured by Debugbar during previous requests.

Can I run EXPLAIN on queries captured by Laravel Debugbar?▼

Yes, use php artisan debugbar:queries {id} --statement=N --explain to get the EXPLAIN plan for a SELECT query. Note that --explain and --result re-execute against the current database, so results may differ from the original request.

Why does debugbar:get show no data for a collector?▼

Collector availability depends on the application's debugbar configuration. Run php artisan debugbar:get {id} without a collector flag first to see the summary of which collectors actually captured data for that request.