# Debug Software with Systematic Strategies

Complex defects waste time when investigation relies on guesswork. This skill applies reproducible experiments, targeted instrumentation, profiling, and verification to identify root causes.

## Install

```bash
npx skillstore add sickn33/debugging-strategies
```

## Metadata

- Status: approved
- Slug: sickn33-debugging-strategies
- Skillstore revision: r2
- Version status: missing
- Tree hash: 74a3fc6ca87ddda721c6349a8a5210de3c2bb08dfadcf12c92ab88778ea247f3
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/debugging-strategies
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands, network
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-debugging-strategies
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-debugging-strategies/manifest

## Capabilities

- Structures investigations around reproduction, evidence gathering, testable hypotheses, controlled experiments, and fix verification.
- Guides regression isolation with binary search, Git history comparison, and git bisect.
- Suggests targeted logging, tracing, assertions, breakpoints, heap snapshots, and CPU profiling.
- Provides debugging examples for JavaScript, TypeScript, Python, and Go.
- Helps compare working and failing environments, data, users, versions, and configurations.
- Creates focused checklists for intermittent bugs, performance problems, and production incidents.

## Use Cases

- Isolate an Application Defect: Turn an error report into reproduction steps, ranked hypotheses, controlled tests, and clear verification criteria.
- Investigate a Production Incident: Compare logs, traces, metrics, deployments, and environments while keeping production changes controlled.
- Diagnose a Performance Regression: Select profiling tools, measure bottlenecks, compare versions, and confirm improvement with repeatable benchmarks.

## Prompt Templates

### Triage an Error

```
Help me debug [error]. Ask for missing reproduction details, then create a short plan to isolate the cause and verify the fix.
```

### Isolate a Regression

```
Analyze this regression: [symptom], last working version [version], current version [version], and recent changes [changes]. Propose a git bisect plan with pass criteria.
```

### Profile a Bottleneck

```
Diagnose [slow operation] using these measurements: [metrics]. Rank likely bottlenecks, choose profiling evidence, and define before-and-after benchmarks.
```

### Analyze a Distributed Incident

```
Investigate this distributed incident using [logs], [traces], [metrics], and [deployment timeline]. Rank hypotheses, define controlled tests, and include rollback and verification criteria.
```

## Limitations

- The skill cannot access applications, logs, traces, debuggers, or runtime environments by itself.
- Useful diagnosis requires an observable symptom and enough evidence to form testable hypotheses.
- Code samples are illustrative and require adaptation to the project language, framework, and safety controls.
- Production investigation still requires access approval, privacy safeguards, rollback planning, and environment-specific testing.

## Best Practices

- Reproduce the symptom and record the exact environment, inputs, errors, and recent changes before proposing a fix.
- Change one variable per experiment and define evidence that would confirm or reject each hypothesis.
- Verify the root-cause fix with the original reproduction, regression tests, and relevant performance measurements.

## Anti Patterns

- Do not make several speculative changes at once because the result will not identify the responsible variable.
- Do not expose secrets, personal data, or production records in logs, traces, prompts, or test fixtures.
- Do not test disruptive hypotheses directly in production without authorization, safeguards, monitoring, and rollback criteria.

## Security Audit

- Audited at: 2026-07-23T23:02:57.287\+00:00
- Summary: All nine static findings are false positives caused by language-agnostic pattern matching. Go import blocks, TypeScript template literals, Markdown code delimiters, and a localhost documentation link are benign. No prompt injection, data exfiltration, or unauthorized command execution was found.

## Stats

- Views: 119
- Downloads: 15
- Favorites: 0
- Popularity score: 0