skills.rest
ai-enhanced-engineer
ai-enhanced-engineerOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dev-debugging-strategies

Diagnose production failures with hypothesis-driven investigation and environment-first triage.

3|Updated Jan 25, 2026
Search Tags:#code analysis#debugging#production#systematic investigation#hypothesis-driven#environment-first
One-click install
npx skills add https://github.com/ai-enhanced-engineer/aiee-skills --skill dev-debugging-strategies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-debugging-strategies
Source: https://github.com/ai-enhanced-engineer/aiee-skills/tree/main/skills/dev-debugging-strategies
Command: npx skills add https://github.com/ai-enhanced-engineer/aiee-skills --skill dev-debugging-strategies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides systematic production debugging patterns to diagnose production failures, investigate regressions, and debug issues without an obvious root cause.

Core Features & Use Cases

  • Hypothesis-Driven Framework: Structure investigations as numbered hypotheses to avoid confirmation bias.
  • Temporal Analysis Filter: Quickly identify regression candidates and static bugs.
  • Environment Before Code: Check infrastructure before diving into application code.
  • CWD-First Diagnostic: Identify issues with Babel/Jest transform errors caused by CWD drift.
  • Deeper Debugging Patterns: Explore CI vs Local Divergence, Webhook & Wire-Level inspection, and Documentation & Review-Bot Loops.
  • Confident False-Negatives: Recognize and avoid tool dialect traps.
  • Anti-Patterns: Identify common debugging mistakes and their solutions.
  • Investigation Audit Pattern: Ensure accuracy and correctness in audits.
  • Evidence-Gathering Commands: Use specific commands for tree membership, mtime listing, and more.
  • Laravel Sanctum Credentials Triage: Triage login issues in Laravel SPAs.
  • Code Review / Sibling Pattern Sweep: Identify and address pattern violations across the codebase.
  • Pre-Commit Hook Stash for Root-Cause Isolation: Isolate pre-commit test failures.
  • Playwright FE↔BE Contract Drift Triage: Inspect FE and BE interactions for issues.
  • Doc-vs-Reality Drift: Verify README claims against implementation.
  • Verifying Review-Bot Findings: Avoid chasing false positives from review bots.
  • Playwright Visual-Verification Loop: Ensure visual correctness of UI features.
  • Git Branch & Merge Hygiene: Maintain clean and efficient git workflows.
  • CI Flake: Assertion Polling vs Click Ordering: Address CI assertion race conditions.
  • Python Logging: Format Values Into the Message: Improve log readability.
  • Specialist-Consult Priming with Full Entity-Space Counts: Provide accurate data for subagents.
  • CI vs Local Divergence: Resolve version mismatches and other CI issues.
  • Frontend: CSS Rules Present but Not Applied: Diagnose CSS rendering issues.
  • Reviewer Blocker Triage: Verify code review blockers.
  • Git Branch Hygiene: Maintain clean git branches.

Quick Start

Use the dev-debugging-strategies skill to investigate a production failure by formulating hypotheses and running diagnostics.

Frequently Asked Questions about dev-debugging-strategies

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

FAQPage Schema
How do I systematically debug production failures without an obvious root cause?▼

Systematic production debugging uses a hypothesis-driven investigation framework to structure diagnostics and avoid confirmation bias. You formulate numbered hypotheses and apply an environment-first triage approach to isolate failures lacking clear root causes.

What is hypothesis-driven investigation and how does it prevent confirmation bias?▼

Hypothesis-driven investigation structures debugging tasks as numbered hypotheses to systematically validate assumptions. By explicitly framing each guess, it prevents confirmation bias and ensures you evaluate evidence objectively before changing application code.

How do I identify regression candidates when investigating static bugs and production failures?▼

Temporal regression analysis filters identify regression candidates by examining timeline changes, distinguishing them from static bugs. This pattern helps quickly narrow down recent modifications that likely introduced the production failure.

Why should I check infrastructure and environment before diving into application code during triage?▼

Environment-first triage checks infrastructure configurations before application code to quickly catch external factors causing production failures. This approach identifies issues like CWD drift causing Babel or Jest transform errors before unnecessary code changes.

How do I resolve CI vs local divergence and version mismatches during debugging?▼

Resolving CI vs local divergence involves checking version mismatches and environment differences between local and CI pipelines. This debugging pattern isolates whether test failures originate from environment variables, dependency versions, or code logic.

What are common debugging anti-patterns that cause false negatives during root cause analysis?▼

Common debugging anti-patterns include ignoring tool dialect traps that generate confident false-negatives, and chasing false positives from review bots. Recognizing these mistakes ensures accurate investigation audits and prevents misdiagnosing production failures.

Related Skills

Explore More Software Engineering Skills→
alex-voloshin-devalex-voloshin-dev
2

analyze-local

Diagnose local Docker environments by analyzing container status, logs, networking, and resource utilization.

Community
Advanced
zangjeicyzangjeicy

requesting-code-review

Scan git diffs for security vulnerabilities and quality regressions.

Community
Advanced
qprjack86qprjack86

count-registry

Read .github/count-manifest.json to provide authoritative repository entity counts.

Community
Basic
LucasdoreacLucasdoreac

Authentication Management

Secure MutuaPIX login flows across Laravel Sanctum and Next.js.

Community
Intermediate