Skip to content
Skills Library
Programming · Building & coding

ditz-bugfix

/ditz-bugfix

Use when something breaks - test, build, or runtime error.

Repository
ditzzzai ↗
Licence
MIT
Last repository change
29.10.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 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 29.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 something breaks - test, build, or runtime error.

Original author description

Use when something breaks - test, build, or runtime error.

How it works

  1. When to Use
  2. Hukum
  3. Protokol
  4. Eskalasi: fix berturut-turut bikin masalah baru
  5. Jangan
Original SKILL.md headings · 56 lines, 403 words
SKILL.md preview
---
name: ditz-bugfix
description: Use when something breaks - test, build, or runtime error.
version: 1.0.0
license: MIT
metadata:
  hermes:
    tags: [debugging, root-cause, triage]
    related_skills: [systematic-debugging, ditz-mission, ditz-code]
---

# ditz-bugfix - Stop, Reproduksi, Akar, Fix, Kunci

## When to Use
- Test gagal, build rusak, perilaku nggak sesuai, error di log.
- "Dulu jalan, sekarang nggak."
- Satu fitur/modul dirasa rusak total → pakai protokol 5 fase di bawah.

## Hukum

```
NGGAK ADA FIX SEBELUM BUG BISA DIREPRODUKSI DAN AKARNYA DIKETAHUI.
```

Kalau belum paham kenapa, perubahan apapun itu tebakan. Tebakan = utang.

## Protokol

**1. STOP.** Jangan nambah fitur, jangan "sekalian rapihin". Jangan push lewat test yang merah - error menumpuk dan ngerusak langkah berikutnya.

**2. Rekam bukti.** Error teks lengkap (bukan potongan), command persisnya, env (versi node/python, OS), langkah reproduksi. Simpen output ke file kalau panjang (`... 2>&1 | tee /tmp/err.log`).

**3. Reproduksi.** Cari cara paling kecil yang gagal konsisten. Kalau nggak bisa direproduksi, itu masalah informasi - jangan nebak fix, tambah logging/tracing dulu.

**4. Lokalisasi.** Persempit:
- Baca stack trace dari frame paling atas yang kode lu sendiri.
- `git log -5 -- <file>` dan `git diff` - apa yang berubah terakhir?
- Bisect manual: matikan separuh, cek, ulang.
- Cek asumsi: versi dependency (`npm ls x`, `pip show x`), env var kosong, file config kebaca, port bentrok, permission, path relatif vs absolut.
- Bahasa-spesifik: Python `python -X dev`, `pdb`/`breakpoint()`; Node `node --inspect`, `NODE_OPTIONS=--trace-warnings`.

**5. Satu hipotesis, satu test.** Tulis: "gue curiga X jadi penyebabnya karena Y". Uji dengan perubahan terkecil. Kalau hipotesis mati, catat dan bikin yang baru. Jangan pernah uji dua hipotesis sekaligus.

**6. Fix di akar, bukan gejala.** Kalau symptom yang dimatiin (try/catch yang nelan error, `setTimeout` nambah delay, retry buta), sebutin eksplisit sebagai tambalan dan alasannya.

**7. Kunci.** Tambah test yang gagal sebelum fix dan lulus sesudahnya. Kalau nggak bisa dites, tulis kenapa di laporan.

**8. Verifikasi.** Jalankan ulang test suite relevan + jalur yang tadi rusak. Kutip hasil nyata.

## Eskalasi: fix berturut-turut bikin masalah baru

Kalau 3+ fix malah munculin masalah baru di tempat lain → **bukan kumpulan bug, tapi masalah arsitektur.** Berhenti. Lapor:

```
3+ fix malah nimbrung masalah baru. Ini bau arsitektur, bukan bug lepas.
Temuan: <ringkas pola yang muncul, mis. shared state / coupling>
Opsi: (a) lanjut tambal (bakal nambah utang), (b) resiko restrukturisasi bagian X
```

## Jangan

- Ngubah 3 hal sekaligus lalu bingung mana yang benerin.
- "Fix" dengan nambah `if (x) return` di banyak tempat.
- Ngeluhin bug ke user tanpa hasil lokalisasi.
- Bilang "udah gua fix" tanpa reproduce → fix → verify.

Versions

The database has no other skills named ditz-bugfix.

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

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 96ditz-tdd
    Use when adding tests or fixing bugs test-first.
  • 86ditz-router
    Use to pick which ditz-* engineering skill fits the task.
  • 90bugfix
    Use when encountering a bug, error, or unexpected behavior that needs diagnosis and fix.
  • 100bugfix-workflow
    End-to-end bugfix workflow. Test first, plan, fix, verify. Use when the user says "fix bug", "bugfix", "investigate issue", "fix #NNN", or any bug-related work. Covers reproduction, test creation, RCA, fix implementation, verification, and ticket documentation.
  • 100bugfix-workflow
    Use when the user says "fix bug", "fix #NNN", or you hit a failing test or reproducible defect that needs fixing end-to-end (not investigation alone). The full bugfix workflow from reproduction through a verified, documented fix.
  • 90sdlc-bugfix
    Explicit-only ADLC bug fixer. Use only when the user invokes $adlc-next:sdlc-bugfix or /adlc-next:sdlc-bugfix with a concrete defect or regression to reproduce, diagnose to its root cause, fix, and guard with a regression check. Not for work that was not delegated through this command.

Feedback and reports

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