Agent skill

Debug Using Debugbar

by hexlet-volunteers in hexlet-volunteers/hexlet-sicp

Inspect what a Laravel request actually did — queries, exceptions, timing, cache, auth, views — by reading the profiling data Laravel Debugbar already captured, via Artisan commands.

AGPL-3.0Auto-check passedBackend & APIs

Install Debug Using Debugbar

skills CLI
$ npx skills add hexlet-volunteers/hexlet-sicp --skill debug-using-debugbar -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hexlet-volunteers/hexlet-sicp debug-using-debugbar --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hexlet-volunteers/hexlet-sicp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debug-using-debugbar .claude/skills/debug-using-debugbar && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debug-using-debugbar
GitHub stars
114
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
478 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Inspect what a Laravel request actually did — queries, exceptions, timing, cache, auth, views — by reading the profiling data Laravel Debugbar already captured, via Artisan commands.

  • Works in 5 steps: Find the relevant request → Inspect the request summary to see which… → Drill into the relevant collector based… → …
  • Investigating a bug
  • SKILL.md covers Debugging and optimizing…, Finding requests, Inspecting a request and Analyzing queries, plus 2 more sections
  • Calls php

What it does

Debug Using Debugbar is an agent skill from hexlet-volunteers/hexlet-sicp. Inspect what a Laravel request actually did — queries, exceptions, timing, cache, auth, views — by reading the profiling data Laravel Debugbar already captured, via Artisan commands. Use when investigating a bug, a slow page or endpoint, an N+1 or duplicate query problem, a failing or slow SQL statement, a 500 or unexpected status code, or when asked to optimize a request. Also covers queued jobs and Artisan commands. Applies even when the user does not mention "debugbar" or "profiling".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires Laravel with fruitcake/laravel-debugbar installed, debug mode enabled, and debugbar.storage.enabled set.

It sits in Backend & APIs, covering Backend development and SQL. It works with Laravel and SQL. The repository describes itself as: Hexlet SICP is a service for those studying the book Structure and Interpretation of Computer Programs. Track your progress and match yourself against others on the global… The licence is AGPL-3.0.

When your agent uses it

  • Investigating a bug
  • Duplicate query problem
  • Slow SQL statement
  • Unexpected status code

Example prompts

  • “debugbar”
  • “profiling”
  • “/debug-using-debugbar”

Requirements

  • Compatibility (from SKILL.md): Requires Laravel with fruitcake/laravel-debugbar installed, debug mode enabled, and `debugbar.storage.enabled` set.

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Find the relevant request
  2. Inspect the request summary to see which collectors have data
  3. Drill into the relevant collector based on the issue type
  4. For query issues, use dedicated query analysis
  5. Trace the problem to source code using backtraces, then fix and re-test.

What it can do on your machine

Read from SKILL.md and the folder at commit 4113c36. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • php

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires Laravel with fruitcake/laravel-debugbar installed, debug mode enabled, and `debugbar.storage.enabled` set.

    From compatibility in the SKILL.md frontmatter.

Context cost

Debug Using Debugbar loads about 1.5k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 478 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hexlet-volunteers/hexlet-sicp at commit 4113c36, republished under its AGPL-3.0 licence (© hexlet-volunteers). 478 words, ~1,476 tokens.

Download SKILL.mdSave it as .claude/skills/debug-using-debugbar/SKILL.md (or your agent's skills folder).
name
debug-using-debugbar
description
Inspect what a Laravel request actually did — queries, exceptions, timing, cache, auth, views — by reading the profiling data Laravel Debugbar already captured, via Artisan commands. Use when investigating a bug, a slow page or endpoint, an N+1 or duplicate query problem, a failing or slow SQL statement, a 500 or unexpected status code, or when asked to optimize a request. Also covers queued jobs and Artisan commands. Applies even when the user does not mention "debugbar" or "profiling".
compatibility
Requires Laravel with fruitcake/laravel-debugbar installed, debug mode enabled, and `debugbar.storage.enabled` set.

Debugging and optimizing workflow

  1. Find the relevant request:
    bash
    php artisan debugbar:find --issues --max=50
  2. Inspect the request summary to see which collectors have data:
    bash
    php artisan debugbar:get {id}
  3. Drill into the relevant collector based on the issue type:
    bash
    php artisan debugbar:get {id} --collector=exceptions
  4. For query issues, use dedicated query analysis:
    bash
    php artisan debugbar:queries {id}
  5. Trace the problem to source code using backtraces, then fix and re-test.

If the storage is empty, there is nothing to debug yet — ask the user to exercise the page or endpoint first, or trigger it yourself, then run debugbar:find again.

Finding requests

bash
# List recent requests (shows summary with status, duration, memory, query count)
php artisan debugbar:find

# Filter by URI pattern (fnmatch) and/or HTTP method
php artisan debugbar:find --uri="/api/*" --method=POST

# Only show requests with issues (exceptions, slow queries, duplicates, errors)
php artisan debugbar:find --issues --max=50

# Customize issue thresholds (defaults: --min-queries=50, --min-duration=1000, --min-duplicates=2)
php artisan debugbar:find --issues --min-queries=10 --min-duration=500

# Threshold options also work standalone, filtering on just that criteria
php artisan debugbar:find --min-queries=20

--issues flags: exceptions, non-2xx status, high query count, slow queries, duplicate query groups, slow request duration, and failed queries. Issue filtering applies on top of the fetched result set — increase --max to scan further back.

Queued jobs and Artisan commands are stored too, with method set to JOB or CLI:

bash
php artisan debugbar:find --method=JOB      # queued jobs
php artisan debugbar:find --method=CLI      # artisan commands

Inspecting a request

bash
# Summary of all collectors (available collectors depend on config)
php artisan debugbar:get latest
php artisan debugbar:get {id}

# Full data for a specific collector
php artisan debugbar:get {id} --collector=exceptions

Pick the collector by issue type:

  • Error/500 → exceptions · Slow page → queries, time · Auth → auth, gate · Cache → cache
  • N+1 / ORM → queries, models · View overhead → views · External calls → http_client
  • Log output → log (Laravel log events), messages (debug() calls), logs (log file tail)

If the collector name is wrong, the command lists the collectors that actually have data for that request.

Analyzing queries

bash
# Overview with duplicate detection, slow flags and failed statements
php artisan debugbar:queries {id}

# Backtrace and params for a specific statement
php artisan debugbar:queries {id} --statement=N

# EXPLAIN plan or re-execute a SELECT
php artisan debugbar:queries {id} --statement=N --explain
php artisan debugbar:queries {id} --statement=N --result

The Flags column marks SLOW and FAILED statements; failed statements are listed again below the table with their driver error.

Two separate repetition reports follow the table, and they mean different things:

  • Duplicate queries — identical SQL and identical bindings. Usually a query that should have been cached or hoisted out of a loop.
  • Repeated query shapes with varying bindings — the same query with a different value each time. This is the classic N+1: an unloaded relation fetched per record. Fix it with eager loading (with()). Detection strips literals from the SQL, so where user_id = 1 and where user_id = 2 count as one shape.

Use --statement=N on any index from those groups to get the backtrace and find the origin.

Show full SKILL.md (163 more words)Show less

JSON output

All three read commands accept --json, which is easier to parse than the tables and preserves exact numbers:

bash
php artisan debugbar:find --issues --json     # array of requests, each with an `issues` list
php artisan debugbar:queries {id} --json      # statements plus `duplicate_groups` and `n_plus_one_groups`
php artisan debugbar:get {id} --json          # raw collector data (`--raw` is the same thing)

Gotchas

  • Always start with debugbar:find --issues rather than debugbar:find — the issue flags surface the most actionable requests immediately.
  • The {id} is the request ID from the debugbar:find output, or use latest to inspect the most recent request.
  • Collector availability depends on the app's debugbar config — the summary from debugbar:get shows which collectors have data.
  • The Dup column only counts exact duplicates (same bindings). For N+1 read the "repeated query shapes" section instead — that is where a per-record lazy load shows up.
  • --explain and --result only work on SELECT queries, and require --statement=N. They re-execute against the current database, so results may differ from the original request.
  • Very large requests are truncated by the debugbar query limits (debugbar.options.db.soft_limit / hard_limit); an info statement in the output says so when it happens.
  • debugbar:clear removes all stored data — use it to reset between debugging sessions, not mid-investigation.

© hexlet-volunteers, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/debug-using-debugbar of hexlet-volunteers/hexlet-sicp.

Open the folder on GitHubat commit 4113c36

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in hexlet-volunteers/hexlet-sicp, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Debug Using Debugbar next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debug Using Debugbar compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debug Using Debugbar this skillhexlet-volunteers/hexlet-sicp1141 repos~1.5kAutomated safety check: PassAGPL-3.0
Arch Wikiahmedemad3/arch-wiki249—~5.1kAutomated safety check: PassNone
Migration CodegenAHS12/thoth-blueprint626—~425Automated safety check: PassGPL-3.0
Geoflowyaojingang/GEOFlow3.8k—~722Automated safety check: PassAGPL-3.0
SQL Migration Generatorjeremylongshore/tons-of-skills-marketplace2.8k—~580Automated safety check: PassMIT
Dsqlawslabs/agent-plugins915—~6.9kAutomated safety check: PassApache-2.0

Similar skills

  • Arch Wiki

    ahmedemad3/arch-wiki

    Scans any project codebase for new/changed modules, endpoints, middleware, infrastructure, Docker topologies, SQL queries, or permissions and updates docs/architecture/architecture.json.

    249 GitHub stars~5.1k tokensUpdated 18 days ago
    Backend & APIsAuto-check passed
  • Migration Codegen

    AHS12/thoth-blueprint

    Change Laravel, TypeORM, or Django migration generation and generated SQL parsing.

    626 GitHub stars~425 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Geoflow

    yaojingang/GEOFlow

    Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration.

    3.8k GitHub stars~722 tokensUpdated today
    Backend & APIsAuto-check passed
  • SQL Migration Generator

    jeremylongshore/tons-of-skills-marketplace

    Generate sql migration generator operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~580 tokensUpdated today
    Backend & APIsAuto-check passed
  • Dsql

    awslabs/agent-plugins

    Official

    Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed…

    915 GitHub stars~6.9k tokensUpdated 2 days ago
    DatabasesAuto-check passed
  • Matlab Connect Databricks

    matlab/matlab-agentic-toolkit

    Connect MATLAB to Databricks via Spark (Databricks Connect) or JDBC (Database Toolbox).

    1.1k GitHub stars~3.5k tokensUpdated today
    Backend & APIsAuto-check passed

More from hexlet-volunteers/hexlet-sicp

  • Socialite Development

    hexlet-volunteers/hexlet-sicp

    Manages OAuth social authentication with Laravel Socialite. An agent skill from hexlet-volunteers/hexlet-sicp.

    114 GitHub starsUsed in 5 repos~1.2k tokens
    Auto-check passed
  • Inertia React Development

    hexlet-volunteers/hexlet-sicp

    Develops Inertia.js v3 React client-side applications. An agent skill from hexlet-volunteers/hexlet-sicp.

    114 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • Laravel Query Builder

    hexlet-volunteers/hexlet-sicp

    Build filtered, sorted, and included API endpoints using spatie/laravel-query-builder.

    114 GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Debug Using Debugbar

What does Debug Using Debugbar do?

Inspect what a Laravel request actually did — queries, exceptions, timing, cache, auth, views — by reading the profiling data Laravel Debugbar already captured, via Artisan commands. Debug Using Debugbar is an agent skill from hexlet-volunteers/hexlet-sicp. Inspect what a Laravel request actually did — queries, exceptions, timing, cache, auth, views — by reading the profiling data Laravel Debugbar already captured, via Artisan commands.

When should I use Debug Using Debugbar?

Debug Using Debugbar fits situations like: investigating a bug; duplicate query problem; slow SQL statement; unexpected status code.

How do I install Debug Using Debugbar in Claude Code?

Run `npx skills add hexlet-volunteers/hexlet-sicp --skill debug-using-debugbar -a claude-code`. Or copy the skill folder (.agents/skills/debug-using-debugbar in hexlet-volunteers/hexlet-sicp) into .claude/skills/debug-using-debugbar in your project. Claude Code loads it when a task matches its description.

How do I install Debug Using Debugbar in Codex?

Run `npx skills add hexlet-volunteers/hexlet-sicp --skill debug-using-debugbar -a codex`. Or copy the skill folder (.agents/skills/debug-using-debugbar in hexlet-volunteers/hexlet-sicp) into .agents/skills/debug-using-debugbar in your project. Codex loads it when a task matches its description.

Can I use Debug Using Debugbar in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hexlet-volunteers/hexlet-sicp --skill debug-using-debugbar -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-using-debugbar, .gemini/skills/debug-using-debugbar, .github/skills/debug-using-debugbar and .opencode/skills/debug-using-debugbar in your project.

What does Debug Using Debugbar need to run?

Going by SKILL.md and its folder, Debug Using Debugbar needs the command-line tools its instructions call (php). Compatibility (from SKILL.md): Requires Laravel with fruitcake/laravel-debugbar installed, debug mode enabled, and `debugbar.storage.enabled` set..

Does Debug Using Debugbar access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Debug Using Debugbar safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Debug Using Debugbar use?

Debug Using Debugbar is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debug Using Debugbar use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Debug Using Debugbar?

Skills that share tags, products or a category with Debug Using Debugbar: Arch Wiki (ahmedemad3/arch-wiki, 249 stars), Migration Codegen (AHS12/thoth-blueprint, 626 stars), Geoflow (yaojingang/GEOFlow, 3.8k stars) and SQL Migration Generator (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug Using Debugbar?

hexlet-volunteers (a GitHub organization) maintains it in hexlet-volunteers/hexlet-sicp, which has 114 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.

Source: hexlet-volunteers/hexlet-sicp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.