Skip to content
Skills Library
Programming · Analysis

debug-triage

/debug-triage

Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.

Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.

Triggers from the description

debug thisfix thiswhy is this broken
Original author description

Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.

How it works

  1. When to activate
  2. Steps
  3. Rules
  4. Output
Original SKILL.md headings · 38 lines, 331 words
SKILL.md preview
---
name: debug-triage
description: Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.
allowed-tools: Read Grep Glob Bash(git log:*) Bash(git blame:*) Bash(git diff:*)
---

# debug-triage

## When to activate

- User pastes a terminal or PowerShell transcript containing an error.
- User pastes a stack trace.
- User says "debug", "fix this", "why is this broken", "what's going on here".

Do NOT activate for refactoring requests, feature work, or general code review -- those are separate tasks.

## Steps

1. **Parse the actual error.** Read stack traces bottom-up. The top frame is usually the symptom; the root cause is deeper in the stack or earlier in the log. Ignore generic first lines like "Traceback (most recent call last):" or "Uncaught Error".
2. **State the likely cause in one sentence.** Not a paragraph. "Null dereference on `user.profile` because the auth middleware returns `null` for unverified emails."
3. **Propose the fix as a diff or command.** Not prose. Either a code snippet showing before/after, or the exact shell command to run.
4. **Name a regression test.** Where it would live (`tests/auth/email_verify_test.py`), and what assertion would catch this bug next time. One line.
5. **Flag sibling updates.** If the fix changes behavior documented in README, CHANGELOG, or any doc file, list them. If not, say "none".

## Rules

- **Don't ask the user to reformat the paste.** Parse whatever they gave you.
- **Fix first, explain if asked.** Don't narrate what the error means at length.
- **Ambiguous errors:** if 2+ causes are equally likely, pick the likeliest and say so in one line. Do not dump all possibilities unless asked.
- **Recent changes are suspect.** Run `git log -5 --oneline -- <file>` on the failing file. If a recent commit touched the failing line, mention it.
- **Environment first.** If the error looks like it could be environmental (missing env var, wrong Node/Python version, CRLF line endings, path with spaces), check the environment before hypothesizing code bugs.

## Output

```text
Cause: <one line>
Fix: <diff or command>
Regression test: <path + what it asserts>
Siblings to update: <list or "none">
```

No preamble. Lead with `Cause:`.

Versions

RepositoryScoreLicence
This page · sagargupta16/claude-skills100MIT
omexit/claude-skills-pack100MIT
iuliandita/skills90MIT

Database snapshot: 13.11.2026 · package version 894174654597 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90error-reading
    Use when the user pastes any error output, stack trace, log, or failure message — structured interpretation before diagnosis
  • 100debug-detective
    Find the root cause of a bug, crash, error message or failing test, then fix it. Use when the user says "this is broken", "why does this fail", "I get this error", "the test is failing", "it worked yesterday", or pastes a stack trace.
  • 90fix
    Diagnose the root cause of a bug and fix it with a regression test, from a description, a stack trace or error output, or a GitHub issue link. Stops with a working tree to review. Use for 'fix this', 'this is broken', a pasted traceback, or an issue link where a patch is…
  • 100debug-production
    Ask your agent why production broke. It reads the error, stack trace, logs, and trace in LogBrew and helps you fix the bug. Use when someone asks why something broke in production, why checkout or login fails, what an error or stack trace means, or to debug a crash, exception,…
  • 100debug-root-cause
    Systematically find and fix the root cause of bugs, errors, failing tests, and crashes in JavaScript/TypeScript and Python. Use whenever the user pastes an error or stack trace, says something is broken, "not working", "error", "kenapa gagal", "bug", a test fails, or behavior is…
  • 100verify-and-fix
    This skill should be used when the user reports an error, bug, or unexpected behavior and wants it diagnosed and fixed. Trigger on phrases like "check this error", "check this bug", "here's an error", "here's a bug", "I have an error", "I have a bug", "found a bug", "got an…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.