skills.rest
BasedHardware
BasedHardwareOFFICIAL
Explore all skills by this author →
Website𝕏@omidotmeGitHub

debug-mode

Guide structured debugging workflows for hypothesis generation, instrumentation, and analysis.

13.1k|2.2k|Updated Mar 22, 2024
Search Tags:#performance#debugging#instrumentation#software-engineering#reproduction#root-cause-analysis#debug-mode
One-click install
npx skills add https://github.com/BasedHardware/omi --skill debug-mode-basedhardware
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-mode
Source: https://github.com/BasedHardware/omi/tree/main/.cursor/skills/debug-mode
Command: npx skills add https://github.com/BasedHardware/omi --skill debug-mode-basedhardware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured Debug Mode workflows to guide teams through hypothesis generation, instrumentation, reproduction, analysis, and targeted fixes, reducing time to root cause and improving reliability.

Core Features & Use Cases

  • Exploration & Hypothesis: Systematically explore code paths and generate root-cause hypotheses.
  • Instrumentation & Monitoring: Insert logs and state tracking to capture runtime behavior.
  • Reproduction & Analysis: Reproduce issues with detailed steps and analyze logs to identify failure patterns.
  • Targeted Fixes & Verification: Apply minimal fixes and verify outcomes while cleaning up instrumentation.

Quick Start

Activate Debug Mode and provide a bug report with reproduction steps. For example: "The application crashes after saving a record; reproduce by logging in, navigating to the record, and clicking Save. Expected: Save succeeds without error; Actual: App crashes with stack trace."

Frequently Asked Questions about debug-mode

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

FAQPage Schema
How do I debug a race condition that only appears in production?▼

Debug a race condition by using structured workflows to generate root-cause hypotheses, insert log instrumentation to capture runtime behavior, reproduce the issue, and analyze failure patterns for targeted fixes.

What's the best way to find the root cause of a software regression?▼

Root-cause analysis for a regression is best done by systematically exploring code paths, generating hypotheses, and reproducing the issue with detailed steps to identify failure patterns and apply minimal fixes.

How do I add instrumentation to track down a tricky bug without cluttering the codebase?▼

Add instrumentation by inserting logs and state tracking to capture runtime behavior during reproduction, then apply minimal fixes and clean up the instrumentation to verify outcomes without codebase clutter.

Can I use a structured debugging workflow for performance issues, or is it just for crashes?▼

A structured debugging workflow can be used for performance issues, tricky bugs, regressions, and race conditions across software systems, not just for application crashes.

How do I reproduce a software bug when I only have a stack trace?▼

Reproduce a bug from a stack trace by using the debug mode workflow to guide exploration, insert state tracking, and analyze logs to identify failure patterns needed for targeted fixes.

Why does my application crash after a specific user action like saving a record?▼

An application crash after saving a record requires structured exploration to generate root-cause hypotheses, followed by log instrumentation and reproduction to analyze the failure pattern and apply a fix.

Related Skills

Explore More Software Engineering Skills→
mopeyjellyfishmopeyjellyfish
1

debug

Reproduce bugs from evidence and prove root causes with red signals.

Community
Advanced
DYAI2025DYAI2025
3

test-driven-development

Enforce the Red-Green-Refactor cycle for all feature work and bug fixes.

Community
Intermediate
Leap0920Leap0920
1

debug

Diagnose OMC/Claude-Code session failures by analyzing logs, traces, and state.

Community
Intermediate
shushuznshushuzn
4

diagnose

Diagnose hard bugs and performance regressions with a reproduce-minimise-hypothesise-instrument-fix-regression-test loop.

Community
Advanced