debugging — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited debugging (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Diagnose and fix errors using scientific method with disciplined root cause analysis.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRSTIf you haven't completed Phase 1, you cannot propose fixes. Symptom fixes are failure.
Use for ANY technical issue:
Use ESPECIALLY when:
Don't skip when:
Complete each phase before proceeding to the next.
BEFORE attempting ANY fix:
#### 1. Read Error Messages Carefully
#### 2. Reproduce Consistently
#### 3. Check Recent Changes
git diff, recent commits#### 4. Trace Data Flow When error is deep in call stack:
See root-cause-tracing.md for the complete backward tracing technique.
#### 5. Gather Evidence in Multi-Component Systems When system has multiple components (API → service → database):
For EACH component boundary:
- Log what data enters component
- Log what data exits component
- Verify environment/config propagation
Run once to gather evidence showing WHERE it breaks
THEN analyze evidence to identify failing component
THEN investigate that specific componentFind the pattern before fixing:
Scientific method:
Fix the root cause, not the symptom:
If you catch yourself thinking:
ALL of these mean: STOP. Return to Phase 1.
| Excuse | Reality |
|---|---|
| "Issue is simple, don't need process" | Simple issues have root causes too. Process is fast for simple bugs. |
| "Emergency, no time for process" | Systematic debugging is FASTER than guess-and-check thrashing. |
| "Just try this first, then investigate" | First fix sets the pattern. Do it right from the start. |
| "Multiple fixes at once saves time" | Can't isolate what worked. Causes new bugs. |
| "I see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. |
| Phase | Key Activities | Success Criteria |
|---|---|---|
| 1. Root Cause | Read errors, reproduce, check changes, trace data | Understand WHAT and WHY |
| 2. Pattern | Find working examples, compare | Identify differences |
| 3. Hypothesis | Form theory, test minimally | Confirmed or new hypothesis |
| 4. Implementation | Create test, fix, verify | Bug resolved, tests pass |
# Git bisect for regressions
git bisect start
git bisect bad HEAD
git bisect good <last-known-good-commit>
# Find recent changes to a file
git log --oneline -10 path/to/file
# Search for error message
grep -r "error message" --include="*.ts"| Error Pattern | Likely Root Cause | Investigation |
|---|---|---|
Cannot read property 'x' of undefined | Missing data, async timing | Trace where null originates |
Module not found | Path issues, missing export | Check exact path, case sensitivity |
CORS error | Backend config | Check Network tab, test with curl |
Timeout | Slow operation, connection issue | Profile, check network |
| Works locally, fails in CI | Environment diff | Compare env vars, versions, permissions |
| Intermittent failures | Race conditions, timing | Look for shared state, async issues |
From debugging sessions:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.