Skip to content
Skills Library
Programming · Building & coding

bug-fix

/bug-fix

Use for localized bugs, runtime errors, white screens, failing tests, console errors, and regressions. Make the smallest safe fix.

Licence
MIT
Last repository change
05.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 05.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 for localized bugs, runtime errors, white screens, failing tests, console errors, and regressions. Make the smallest safe fix.

Arguments

/bug-fix [error message, stack trace, or failing test]
Original author description

Use for localized bugs, runtime errors, white screens, failing tests, console errors, and regressions. Make the smallest safe fix.

How it works

  1. Output
Original SKILL.md headings · 20 lines, 152 words
SKILL.md preview
---
name: bug-fix
description: Use for localized bugs, runtime errors, white screens, failing tests, console errors, and regressions. Make the smallest safe fix.
allowed-tools: Read, Grep, Glob, Bash, Edit, Write
when_to_use: Use automatically when something that worked is now broken and the cause is localizable.
argument-hint: "[error message, stack trace, or failing test]"
---

# bug-fix

Read error → root cause → smallest fix → test → done.

1. Read stack trace / error / failing test first. Open ONLY files in the stack trace or directly symptom-related.
2. Fix the smallest responsible code path. Run targeted test — no test exists → add 1 regression test. Non-obvious fix → the why goes in the ROOT line and the commit message, never a code comment.
3. No suspect file in the evidence, or the first fix did not hold → in the main loop switch to `systematic-debug`; inside an agent return `ESCALATE TO: systematic-debug — main loop, [evidence so far]`. Escalate immediately: auth/session/token/payment → security-guard | DB corruption/schema/migration → db-guard.

Deep reference: `${CLAUDE_PLUGIN_ROOT}/agent_docs/error-handling-patterns.md` — typed error hierarchies, boundary handling, retry/fallback patterns.

## Output

```text
ROOT: [what and where]
FIX: [file:line — what changed]
TEST: [command — ✓ | regression test added]
RISK: low | medium
```

Versions

RepositoryScoreLicence
This page · mtvrkan/senior-dev-kit100MIT
nexus-substrate/nexus-agents100MIT
devicedaw/device100AGPL-3.0
ramboz/jig100MIT
ramboz/jig100MIT
ramboz/jig100MIT
sd0xdev/sd0x-harness100MIT
pronskiy/php-src-developer100MIT
chrisallenlane/claude-swe-workflows100MIT

Database snapshot: 13.11.2026 · package version 202378b33d9b (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

  • 90fix-issues
    Use when fixing software issues in a repository, including bug reports, failing tests, CI failures, compile errors, runtime errors, regressions, dependency problems, and requests such as "fix this issue", "resolve this bug", "make tests pass", or "address the failure". Guides…
  • 100awesome-bug-fix
    Fixes a bug through a runnable reproduction and its root cause. Use for errors, crashes, failing tests or builds, flaky behavior, or repeated failed fixes.
  • 100bug-hunt
    Use when reproducing, isolating, and fixing a bug with the smallest safe change.
  • 96testing
    Use when writing, changing, or reviewing tests, or when fixing a bug.
  • 90bug-triage
    Use when the user reports a bug, regression, runtime error, failing build, or broken test and wants reproduction, diagnosis, root-cause analysis, or an authorized fix. Isolates the shared cause and verifies the smallest relevant change.
  • 90fix-loop
    Use when a Java app that has stacktale installed is failing — after running it or its tests, to find what broke, fix it, and confirm the fix by re-running and checking for new errors. Also use when asked to "check the errors", "what's failing", or to work through errors-ai.log.

Feedback and reports

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