Skills debugging-strategies

📦

debugging-strategies

Name: debugging-strategies
Author: sickn33

Content revision r2 Safe ⚡ Contains scripts⚙️ External commands🌐 Network access

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.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "debugging-strategies" from https://skillstore.io/skills/sickn33-debugging-strategies.md and its manifest at https://skillstore.io/api/skills/sickn33-debugging-strategies/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-debugging-strategies.md Signed manifest GET /api/skills/sickn33-debugging-strategies/manifest Signed lockfile GET /api/skills/sickn33-debugging-strategies/lockfile

Test it

Using "debugging-strategies". Checkout requests fail after deployment, but only for large orders.

Expected outcome:

Leading hypothesis: the deployment changed validation or resource limits for large payloads.
Compare order sizes, deployment differences, request limits, and logs from working and failing requests.
Run one controlled boundary test, apply the fix in staging, and repeat the original reproduction.

Using "debugging-strategies". An API became slower after a dependency update.

Expected outcome:

Establish latency and resource baselines for both dependency versions.
Profile database calls, synchronous input and output, allocation pressure, and external service timing.
Confirm the cause by changing one variable and repeating the same benchmark.

Using "debugging-strategies". A service fails intermittently during peak traffic.

Expected outcome:

Correlate failures with load, timing, state transitions, deployments, and dependency health.
Prioritize race conditions, resource exhaustion, timeouts, and out-of-order asynchronous work.
Add focused tracing and stress tests, then verify recovery and recurrence behavior.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

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.

Files scanned

555

Lines analyzed

Review items

False positives ignored

Risk Factors

⚡ Contains scripts (2)

resources/implementation-playbook.md:254-258 resources/implementation-playbook.md:282-285

⚙️ External commands (5)

resources/implementation-playbook.md:339-341 resources/implementation-playbook.md:341-354 resources/implementation-playbook.md:385-388 SKILL.md:33 SKILL.md:37

🌐 Network access (1)

resources/implementation-playbook.md:279

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-debugging-strategies/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-debugging-strategies/security.svg)](https://skillstore.io/skills/sickn33-debugging-strategies?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-debugging-strategies?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-debugging-strategies/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-debugging-strategies.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). debugging-strategies security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-debugging-strategies/audits/5

BibTeX citation

@techreport{sickn33-sickn33-debugging-strategies-2026,
  author = {sickn33},
  title = {debugging-strategies security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-debugging-strategies/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "debugging-strategies security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-debugging-strategies/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-debugging-strategies:audit:5"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

sickn33 Recommended Current

sickn33-debugging-strategies

Skillstore Score 79

Evidence Confidence High

Skillstore usage 15

Updated

2026-08-21

wshobson

wshobson-debugging-strategies

Skillstore Score 77

Evidence Confidence High

Skillstore usage 13

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

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.

Frequently Asked Questions

Which programming languages does this skill support?

The playbook includes JavaScript, TypeScript, Python, and Go examples. Its investigation process also applies to other languages.

Does this skill run commands or modify my project?

No. It provides investigation guidance and examples. You decide which tools, commands, and changes are appropriate.

Can I use it during a production incident?

Yes. Provide sanitized logs, traces, metrics, and deployment context. Follow your access, privacy, change-control, and rollback procedures.

What information should I provide first?

Provide the observed behavior, expected behavior, reproduction steps, complete errors, environment details, and recent changes.

Can it help with performance problems?

Yes. It can organize profiling, baseline comparison, bottleneck hypotheses, controlled measurements, and verification benchmarks.

Will it always identify the root cause?

No. Results depend on available evidence and reproducibility. The skill narrows uncertainty but cannot guarantee access to the responsible system state.