skills.rest
BuildSmarterAI
BuildSmarterAICOMMUNITY
Explore all skills by this author →
GitHub

debugging-playbook

Guide triage, log review, and reproduction for production incidents.

Updated Mar 31, 2026
Search Tags:#debugging#troubleshooting#edge-functions#cloud-run#pdf-processing#production-issues#rlspolicy
One-click install
npx skills add https://github.com/BuildSmarterAI/claude-skills --skill debugging-playbook-buildsmarterai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-playbook
Source: https://github.com/BuildSmarterAI/claude-skills/tree/main/debugging-playbook
Command: npx skills add https://github.com/BuildSmarterAI/claude-skills --skill debugging-playbook-buildsmarterai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline and standardize the discovery and resolution of production failures across Supabase Edge Functions, Google Cloud Run services, RLS policies, PDF processing, and AI extraction pipelines.

Core Features & Use Cases

  • Triage templates and checklists to quickly identify root causes.
  • Cross-layer guidance covering frontend, edge, and database issues with reproducible steps.
  • Case examples: debugging a failing Edge Function, a Cloud Run timeout, or a misbehaving RLS policy.

Quick Start

Inspect a failing deployment by starting with logs and error messages, then follow the step-by-step triage guide.

Frequently Asked Questions about debugging-playbook

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

FAQPage Schema
How do I systematically debug a failing Supabase Edge Function in production?▼

To debug a failing Supabase Edge Function, start by reviewing logs and error messages, then follow a structured triage guide with step-by-step reproduction steps and device-specific checks to identify the root cause.

What is the best way to troubleshoot Cloud Run service timeouts?▼

The best way to troubleshoot Cloud Run timeouts involves systematically identifying the issue through log review and applying structured error-handling guidance with fallback paths for fast recovery.

How do I find the root cause of a misbehaving Supabase RLS policy?▼

Finding the root cause of a misbehaving RLS policy requires cross-layer guidance that covers database issues, utilizing triage templates and structured evidence collection to document the production failure accurately.

Can I use this structured debugging approach for PDF processing failures?▼

Yes, you can use this structured debugging approach for PDF processing failures and AI extraction pipelines, applying standardized triage templates and reproducible steps to quickly identify and resolve production issues.

What steps should I follow to reproduce a production issue across different layers?▼

To reproduce a production issue across different layers, follow structured steps that guide you through triage, log review, and evidence collection, ensuring cross-layer checks spanning frontend, edge, and database components.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
fmflurryfmflurry
171

build-description-test-error-resolution

Identify exact failures and affected scope to patch root causes with targeted tests.

Community
Advanced
kcns008kcns008
4

observability

Analyzes Prometheus/Grafana metrics and logs for Kubernetes and OpenShift incident response.

Community
Advanced
backengineeringbackengineering
434

dynamic-instrumentation

Instrument binaries and trace runtime behavior using LLVM infrastructure.

Official
Advanced