debug-using-debugbar

Diagnose Laravel performance issues by querying Debugbar data via Artisan CLI.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/beardcoder/mens-circle --skill debug-using-debugbar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-using-debugbar
Source: https://github.com/beardcoder/mens-circle/tree/main/.agents/skills/debug-using-debugbar
Command: npx skills add https://github.com/beardcoder/mens-circle --skill debug-using-debugbar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slow and failing Laravel requests impede user experience; Debugbar helps identify exceptions, slow queries, and duplicate work by exposing collected data during a request.

Core Features & Use Cases

  • Inspect request summaries and collector data to identify issues.
  • Drill into exceptions, queries, time, and authentication collectors to locate root causes.
  • Use Artisan CLI commands to reproduce, trace, and fix issues in development.

Quick Start

Begin by running php artisan debugbar:find --issues to locate problematic requests, then inspect details with php artisan debugbar:get {id}.

Frequently Asked Questions about debug-using-debugbar

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

FAQPage Schema
How do I use Laravel Debugbar to find slow requests and duplicate queries?

Laravel Debugbar exposes collected request data to identify slow queries and duplicate work. You can query this data via the Artisan CLI using the debugbar:find --issues command to locate problematic requests.

How do I troubleshoot failing HTTP responses and exception traces in Laravel?

Troubleshoot failing HTTP responses by drilling into Debugbar exception and authentication collectors. Query the collected debug data through the Artisan CLI to trace and reproduce issues during development.

Do I need debug mode enabled to access Laravel Debugbar collector data?

Yes, Laravel debug mode must be enabled. The workflow requires Laravel and the fruitcake/laravel-debugbar package to be installed, and debug mode active to collect and query request data via Artisan.

What is the best way to inspect specific request details after finding Laravel performance issues?

Inspect specific request details by running the Artisan command php artisan debugbar:get {id}. This retrieves detailed collector data for a single request to locate root causes of performance issues.

Can I use Artisan CLI to diagnose Laravel performance issues without manually checking web pages?

Yes, the Artisan CLI allows you to query Debugbar data directly. Run php artisan debugbar:find --issues to locate problematic requests, then inspect collector details without loading web pages.

What collectors are available to diagnose slow pages and exceptions in Laravel?

Debugbar provides collectors for exceptions, queries, time, and authentication. Drill into these specific collectors to locate the root causes of slow pages and failing requests in Laravel.