dev-debugging

Diagnose and fix Capsem bugs through a test-driven three-step debugging workflow.

68|10|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/google/capsem --skill dev-debugging-google
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-debugging
Source: https://github.com/google/capsem/tree/main/skills/dev-debugging
Command: npx skills add https://github.com/google/capsem --skill dev-debugging-google

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging methodology for Capsem helps teams investigate bugs, test failures, and unexpected behavior by enforcing a disciplined, test-driven workflow. It prevents rushing to patches without understanding underlying causes and guides teams through a reproducible diagnostic process.

Core Features & Use Cases

  • Enforces a three-step debugging process (reproduce with a test, diagnose root cause, deliver a comprehensive fix) to improve reliability.
  • Provides structured guidance for VM-level issues, telemetry gaps, networking/policy misconfigurations, and frontend/build pipeline failures.
  • Encourages documentation and pattern-based fixes to prevent repeated regressions across the codebase.

Quick Start

Reproduce the issue with a failing test, diagnose the root cause, and implement a robust fix following the three-step workflow.

Frequently Asked Questions about dev-debugging

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

FAQPage Schema
What is a test-driven debugging workflow for fixing Capsem bugs?

A test-driven debugging workflow enforces a three-step process to fix Capsem bugs: reproduce the issue with a failing test, diagnose the root cause, and then deliver a comprehensive fix to prevent untested patches.

How do I diagnose the root cause of VM-level issues or telemetry gaps in Capsem?

To diagnose root causes in Capsem, you must first reproduce the VM-level or telemetry issue with a test. This structured diagnosis prevents rushing to code patches before fully understanding the underlying misconfiguration or failure.

How to fix networking or policy misconfigurations in Capsem without introducing regressions?

Fix networking or policy misconfigurations by following a structured debugging workflow: reproduce the failure with a test, identify the root cause, and apply a comprehensive fix. This pattern-based approach prevents repeated regressions across components.

Can I use this debugging workflow for frontend and build pipeline failures across Capsem components?

Yes, this debugging workflow applies to frontend and build pipeline failures across Capsem components. It provides structured guidance to ensure fixes are comprehensive and rooted in test-driven diagnosis rather than rushed patches.

Why does Capsem prevent code patches before understanding the root cause of a failure?

Capsem debugging guards prevent code patches before root cause analysis to stop rushed fixes. By requiring a failing test to reproduce the issue first, teams ensure they fully understand the failure before delivering a robust fix.

What is the best way to debug unexpected behavior or test failures in Capsem?

The best way to debug unexpected behavior in Capsem is using a disciplined, test-driven workflow. By enforcing a formal process of reproduction, root cause diagnosis, and comprehensive fixing, it improves reliability and prevents repeated regressions.