debug-using-debugbar

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

Updated May 26, 2026
One-click install
npx skills add https://github.com/rmethodm/resumegen --skill debug-using-debugbar-rmethodm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-using-debugbar
Source: https://github.com/rmethodm/resumegen/tree/main/.agents/skills/debug-using-debugbar
Command: npx skills add https://github.com/rmethodm/resumegen --skill debug-using-debugbar-rmethodm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging Laravel performance issues and errors often means digging through logs or reproducing requests manually. This Skill lets you inspect requests already captured by Laravel Debugbar directly from the terminal, surfacing slow pages, duplicate queries, and exceptions without opening a browser. ## 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, gate, cache) for any captured request. - Query Analysis: Detect duplicate queries signaling N+1 problems, view backtraces for individual statements, and run EXPLAIN plans or re-execute SELECT queries. - Use Case: A page suddenly loads slowly. Run php artisan debugbar:find --issues to spot the slow request, then php artisan debugbar:queries {id} to find duplicate queries, and use --statement=N to trace the offending query back to its source code. ## Quick Start Ask the AI to find recent requests with issues using the debugbar Artisan commands and identify any slow queries or exceptions.

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 exceptions. You can adjust thresholds with --min-duration and --min-queries, and filter by URI pattern or HTTP method.

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

Run php artisan debugbar:queries {id} on a captured request to see duplicate query groups, which are a strong N+1 signal. Use --statement=N to view the backtrace and locate the exact source code issuing the repeated query.

Does this debugging approach require Laravel Debugbar installed?▼

Yes, it requires the fruitcake/laravel-debugbar package installed with debug mode enabled so requests are captured. Collector availability also depends on your application's debugbar configuration.

Can I re-run a captured query to see its execution plan?▼

Yes, use php artisan debugbar:queries {id} --statement=N --explain to get the EXPLAIN plan, or --result to re-execute it. These only work on SELECT queries and run against the current database, so results may differ from the original request.

Why does debugbar:find --issues show no results?▼

Issue filtering applies only to the fetched result set, so older problematic requests may be missed. Increase --max to scan further back, or lower thresholds like --min-queries and --min-duration to catch more requests.