Cbdebugger

Collection of skills for the ColdBox Platform and Claude Plugin

Install

npx -y skills add ColdBox/skills --skill cbdebugger

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when installing, configuring, or using the CBDebugger visual debugging panel in a ColdBox application. Covers enabling the panel in development, performance profiling, SQL query tracking, cache monitoring, request inspection, and ensuring the debugger is disabled in production.

SKILL.md

2.6 KB, 518 tokens by cl100k_base, as published. Nobody here has run it

CBDebugger Skill

When to Use This Skill

Load this skill when:

Installing or enabling the CBDebugger module
Diagnosing performance bottlenecks in development
Tracking SQL queries and their execution times
Inspecting RC/PRC/CGI scopes during debugging
Configuring the debugger to appear only in specific environments
Ensuring debugger is never exposed to end-users in production

Installation

box install cbdebugger

Configuration

Always gate the debugger behind an environment check:

// config/ColdBox.cfc
moduleSettings = {
    cbdebugger = {
        // Only enable in development — never expose in production
        enabled        = getSetting( "environment" ) == "development",
        renderDebugPanel = true,
        expanded       = false,         // collapse panel by default

        // Optional: restrict to specific IPs
        ipList         = "127.0.0.1",   // comma-separated list

        // Profiling options
        showTracers    = true,
        queryMonitor   = {
            enabled    = true,
            logQueries = false          // set true to log all queries
        }
    }
}

Features

Feature	Description
Performance Profiling	Request timings and execution paths
SQL Query Tracking	All DB queries with execution time and bindings
Cache Monitoring	CacheBox statistics and operations
Request Inspection	RC, PRC, CGI, form, and URL scopes
Tracer Messages	Custom `tracer()` calls inline in code
Exception Detail	Full stack traces with local variable context

Usage in Handlers / Flow

// Add a debug tracer message (only visible when debugger is enabled)
tracer( "About to call payment service", { orderId : rc.orderId } )

// Then continue your logic
paymentService.charge( rc.orderId )

Production Safety Checklist

enabled must evaluate to false in staging and production
Never deploy with ipList empty and enabled = true on a public server
Use getSetting("environment") or .env variables — not hard-coded true
Panel renders at bottom of HTML responses — harmless when disabled but wasteful at scale

Documentation

Full documentation: https://coldbox-debugger.ortusbooks.com

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most debug triage skills give in 518 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

Investigate root cause before proposing any fixin 102 of 839, across 67 files
Read error messages completelyin 89 of 839, across 49 files
Create a failing test case before fixingin 84 of 839, across 46 files
Reproduce the issue consistentlyin 82 of 839, across 41 files
Change one variable at a timein 82 of 839, across 42 files
Check recent changesin 74 of 839, across 36 files
Write the regression test before fixingin 74 of 839, across 40 files
Fix the root cause not the symptomin 60 of 839, across 45 files
Implement a single fix at a timein 59 of 839, across 20 files
Trace data flow backward to the sourcein 50 of 839, across 20 files
Remove all debug instrumentationin 49 of 839, across 13 files
Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

install cbdebugger
gate debugger behind environment check
enable debugger only in development
restrict panel access to specific IPs
disable debugger in staging and production
use environment variables to enable debugger

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.