Results for “cdp-debugging”

Capture a full DevTools-protocol trace of any browser automation, bisect the stream into per-page searchable buckets, and attach a trace to an in-progress session for debugging.

Debug application issues with techniques for Python, JavaScript, performance profiling, production incidents, and network problems.

Analyze core dumps, debug live processes, and investigate crashes, deadlocks, and memory issues in C/C++ programs using GDB with source code correlation.

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

Handles containerization, CI/CD pipelines, and deployment setup.

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs.

Debug Python: pdb REPL + debugpy remote (DAP).

Detects insider data exfiltration by analyzing DLP policy violations, file access patterns, upload volume anomalies, and off-hours activity in endpoint and cloud logs using pandas for behavioral analytics and statistical baselines.

Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

Debugging is the scientific method under time pressure.

Debug issues by investigating logs, database state, and git history

Diagnoses Redpanda broker and cluster health using debug bundles, metrics endpoints, logs, CPU profiling, and partition/raft checks, with triage playbooks for common failure modes.

Diagnose failures from runtime evidence before editing code.

Debug Python code interactively with pdb and debugpy, covering local breakpoints, post-mortem analysis, and remote attachment to running processes.

Systematic debugging workflow for errors and bugs. Use when debugging errors, investigating bugs, troubleshooting issues, or when something isn't working as expected. Integrates Sentry MCP for production error context, Firecrawl for researching fix patterns, and Sequential Thinking for complex multi-step diagnosis.

Debugging command. Activates DEBUG mode for systematic problem investigation.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Connect to an existing Chrome browser via Chrome DevTools Protocol to navigate, click, type, screenshot, evaluate JavaScript, read the accessibility tree, and monitor console or network events.

Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance ...

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

GDPR and CCPA/CPRA privacy compliance audit for codebases. Inventories PII fields (email, phone, SSN, IP, device ID, geolocation, biometrics, behavioral data), maps data collection points (forms, APIs, cookies, analytics, error tracking), audits consent mechanisms (cookie banners, opt-in, pre-checked boxes, consent withdrawal), verifies data subject rights implementation (right to access, erasure, rectification, portability, opt-out, Do Not Sell), traces third-party data sharing (Google Analytics, Facebook Pixel, Stripe, SendGrid, Sentry), and checks data retention policies and automated purging. Use when auditing privacy compliance, building data export or deletion endpoints, reviewing cookie consent, or assessing DSAR readiness.

Provides a structured debugging workflow for diagnosing errors, test failures, and unexpected behavior, including root cause analysis and fix verification.

Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.

Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance best practices. Use when: segment, analytics.js, customer data platform, cdp, tracking plan.

Provides a structured debugging workflow for diagnosing errors, test failures, and unexpected behavior, including root cause analysis and verification steps.

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

Step-by-step debugging workflow: reproduce the bug, isolate the failing component, trace to root cause, apply a targeted fix, and verify the fix resolves the issue without regressions. Use when you encounter a bug, error, exception, crash, or unexpected behavior that needs troubleshooting.

GDB debugging assistant for AI agents - analyze core dumps, debug live processes, investigate crashes and deadlocks with source code correlation

Configure, optimize, and troubleshoot CDN deployments with caching strategies, security hardening, and multi-provider management.

Investigates hard, flaky, or performance failures through a six-phase feedback-loop-first debugging process; use when quick targeted debugging is insufficient.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.