Skip to content
Back to skills

Auto Debug

ASecurity

--- name: auto-debug description: Automatically detect bugs from terminal output and suggest/apply fixes without manual intervention ---

  • 33 stars
  • 0 votes
  • 2 copies
  • 3 views
  • Added February 10, 2026
developmentjavascripttypescriptpythonjavabashtestingdebuggingdatabase

Works with

  • terminal

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned February 12, 2026

npx -y skills add lovedragonball/power-ranger-toolkit --skill auto-debug --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Auto Debug?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Auto Debug
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/lovedragonball-auto-debug/badge)](https://www.skillsdirectory.com/skills/lovedragonball-auto-debug)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# πŸ› Auto Debug Skill

---
name: auto-debug
description: Automatically detect bugs from terminal output and suggest/apply fixes without manual intervention
---

## 🎯 Purpose

ΰΈ•ΰΈ£ΰΈ§ΰΈˆΰΈˆΰΈ±ΰΈš errors จาก terminal output ΰΈ­ΰΈ±ΰΈ•ΰΉ‚ΰΈ™ΰΈ‘ΰΈ±ΰΈ•ΰΈ΄ แΰΈ₯ะแนะนำหรือแก้ไขปัญหาทันทม ΰΈ₯ΰΈ”ΰΉ€ΰΈ§ΰΈ₯ΰΈ² debug ΰΈ₯ΰΈ‡ΰΈ­ΰΈ’ΰΉˆΰΈ²ΰΈ‡ΰΈ‘ΰΈ²ΰΈ

## πŸ“‹ When to Use

- ΰΉ€ΰΈ‘ΰΈ·ΰΉˆΰΈ­ terminal แΰΈͺΰΈ”ΰΈ‡ error messages
- ΰΉ€ΰΈ‘ΰΈ·ΰΉˆΰΈ­ build/compile fail
- ΰΉ€ΰΈ‘ΰΈ·ΰΉˆΰΈ­ tests fail
- ΰΉ€ΰΈ‘ΰΈ·ΰΉˆΰΈ­ runtime errors occur
- ΰΉ€ΰΈ‘ΰΈ·ΰΉˆΰΈ­ linting errors เกิดขย้น

## πŸ”§ Capabilities

### 1. Error Detection
| Error Type | Detection Pattern |
|------------|-------------------|
| TypeScript | `TS\d+:`, `Type error:` |
| ESLint | `error:`, `warning:` |
| Runtime | `Error:`, `Exception:` |
| Build | `ENOENT`, `Cannot find module` |
| Test | `FAIL`, `Expected.*but received` |

### 2. Common Error Fixes

#### TypeScript Errors
```typescript
// TS2322: Type 'string' is not assignable to type 'number'
// Fix: Change variable type or value

// TS2339: Property does not exist
// Fix: Add property to interface or use optional chaining

// TS7006: Parameter implicitly has 'any' type
// Fix: Add explicit type annotation
```

#### Module Errors
```bash
# Cannot find module 'xyz'
# Fix 1: npm install xyz
# Fix 2: Check import path spelling
# Fix 3: Add to tsconfig paths

# Module not found: Can't resolve './component'
# Fix: Check file exists, check extension, check case sensitivity
```

#### Runtime Errors
```javascript
// TypeError: Cannot read property 'x' of undefined
// Fix: Add null check or optional chaining

// ReferenceError: variable is not defined
// Fix: Declare variable or check scope

// SyntaxError: Unexpected token
// Fix: Check JSON format, missing brackets
```

## πŸ“ Auto-Debug Process

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  Error Occurs   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
         β”‚
         β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Parse Error Msg β”‚ ← Extract error type, location, message
β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
         β”‚
         β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Identify Cause  β”‚ ← Match patterns, analyze context
β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
         β”‚
         β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Generate Fix    β”‚ ← Create solution based on error type
β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
         β”‚
         β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Apply & Verify  β”‚ ← Apply fix, re-run to verify
β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
         β”‚
         β–Ό
   Fixed? ────No────▢ Try alternative fix
         β”‚
        Yes
         β”‚
         β–Ό
      Done! βœ…
```

## πŸ”„ Auto-Fix Loop

```python
MAX_ATTEMPTS = 5
attempt = 0

while error_exists and attempt < MAX_ATTEMPTS:
    error = parse_error(terminal_output)
    fix = generate_fix(error)
    apply_fix(fix)
    result = run_command_again()
    
    if result.success:
        log_solution(error, fix)  # Save for future
        break
    else:
        attempt += 1
        try_alternative_fix()
```

## πŸ“š Error Pattern Database

### Build Errors
| Pattern | Cause | Auto-Fix |
|---------|-------|----------|
| `ENOENT` | File not found | Check path, create file |
| `EACCES` | Permission denied | Check permissions |
| `EADDRINUSE` | Port in use | Kill process or change port |

### Dependency Errors
| Pattern | Cause | Auto-Fix |
|---------|-------|----------|
| `peer dep` | Version mismatch | Update package |
| `ERESOLVE` | Conflict | Use --legacy-peer-deps |
| `not found` | Missing package | npm install |

### Syntax Errors
| Pattern | Cause | Auto-Fix |
|---------|-------|----------|
| `Unexpected token` | Typo, missing bracket | Add missing syntax |
| `Unterminated string` | Missing quote | Add closing quote |
| `Invalid JSON` | Malformed JSON | Fix JSON syntax |

## βœ… Self-Check

- [ ] Error correctly identified
- [ ] Root cause understood
- [ ] Fix is safe (won't break other code)
- [ ] Fix verified by re-running
- [ ] Solution logged for future reference

## πŸ“’ Announcement Format

```
[πŸ› Auto-Debug] Detected: {error type}
[πŸ› Auto-Debug] Cause: {root cause}
[πŸ› Auto-Debug] Fixing: {applying fix}
[πŸ› Auto-Debug] βœ… Fixed: {summary}
```

## πŸ”— Related Skills

- `debugging` - Manual debugging
- `error-recovery` - Graceful error handling
- `testing` - Prevent errors with tests

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…