Skip to content
Back to skills

Debug Craft Systematic Bug Hunt Elixir

ASecurity

Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsbashdebugginggit

Works with

  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill debug-craft-systematic-bug-hunt-elixir --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Debug Craft Systematic Bug Hunt Elixir?

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

Security grade badge for Debug Craft Systematic Bug Hunt Elixir
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-debug-craft-systematic-bug-hunt-elixir/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-debug-craft-systematic-bug-hunt-elixir)

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
---
name: debug-craft-systematic-bug-hunt-elixir
description: "Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure."
---
# Hunt bugs systematically (Elixir)

> Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure.

**Track:** 🧰 Engineering Essentials · **Domain:** Debugging Craft · **Level:** foundation · **~30 min**

**Who this is for:** All Software Engineers

## When to Use This Skill

Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Steps

1. Reproduce deterministically first; flaky repro = flaky fix
2. Write failing test capturing the bug before touching source
3. Bisect history or code path until minimal failing case remains
4. Form ONE hypothesis, predict its observable, then check
5. Fix root cause, not nearest symptom; add regression test
6. Document the hunt briefly for future searchers
7. Inspect supervision trees and mailbox depths via :observer
8. Benchmark with Benchee; watch BEAM scheduler reductions

## Common Pitfalls

- Shotgun changes stacking unknown unknowns
- Fixing symptoms while root cause ships elsewhere

## Commands

**Install with skills CLI**
```bash
npx skills add aniruddhaadak80/skills --skill debug-craft-systematic-bug-hunt-elixir
```

**Install globally**
```bash
npx skills add aniruddhaadak80/skills --skill debug-craft-systematic-bug-hunt-elixir -g
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills

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…