What happens if the root cause cannot be identified immediately?

The skill follows a fail-fast validation model. If data is insufficient or an investigation path is blocked, it will pause, report the 'blocked' status, and ask for the specific missing context.

What information do I need to provide to use this skill effectively?

You should provide observable symptoms like error messages or stack traces, recent deployment context, and any specific environment constraints you are working under.

Is this skill safe to use on production systems?

Yes, it is designed with safety in mind. It prefers non-destructive commands, redacts secrets and credentials, and requires explicit user confirmation for any risky actions.

How does Systematic Debugging differ from standard AI code fixing?

Standard fixing often involves speculative edits, while Systematic Debugging prioritizes evidence and reproducible logs before suggesting any changes, preventing 'guess-and-check' cycles.

Systematic Debugging

Name: Systematic Debugging
Author: jscraik

byjscraik

•

보안 및 테스팅

Diagnoses production bugs and regressions using evidence-based analysis and reproducible fix plans before implementing code changes.

Systematic Debugging is a specialized runbook designed to shift the AI's approach from speculative code fixing to evidence-driven root cause analysis. It enforces a structured diagnostic workflow that prioritizes stabilizing the scope, isolating components, and verifying hypotheses before any code changes are applied. By requiring observable symptoms and recent deployment context, this skill ensures that fixes are based on confirmed data rather than guesses, significantly reducing the risk of side effects and incomplete resolutions in complex software environments.

주요 기능

012 GitHub stars

02Layered component isolation to identify where system signals drop

03Evidence-based diagnostic planning and prioritized hypothesis generation

04Hypothesis-driven verification loops for minimal, targeted checking

05Non-destructive investigation constraints with secret redaction

06Fail-fast validation with explicit blocked, partial, or complete status reporting

사용 사례

01Investigating intermittent CI/CD test failures or timeouts to find the regression point

02Root-cause analysis of unexpected software behavior following a recent refactor or deployment

03Diagnosing production 500 errors triggered by specific feature flags or environment variables

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jscraik/agent-skills systematic-debugging

For use in Claude.ai and ChatGPT

주요 기능

012 GitHub stars

02Layered component isolation to identify where system signals drop

03Evidence-based diagnostic planning and prioritized hypothesis generation

04Hypothesis-driven verification loops for minimal, targeted checking

05Non-destructive investigation constraints with secret redaction

06Fail-fast validation with explicit blocked, partial, or complete status reporting

사용 사례

01Investigating intermittent CI/CD test failures or timeouts to find the regression point

02Root-cause analysis of unexpected software behavior following a recent refactor or deployment

03Diagnosing production 500 errors triggered by specific feature flags or environment variables

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jscraik/agent-skills systematic-debugging

For use in Claude.ai and ChatGPT