Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
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 9/29/2026
ai-agentsbashdebugginggit

Works with

cli

Security Analysis

A100/100

Scanned 9/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 automatically 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
Files
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

aniruddhaadak80aniruddhaadak80
View sourceSee grades on GitHubMore from aniruddhaadak80 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →