DilawarShafiq/nietzschian-debugger: The anti-AI debugger. What would not kill your code makes it stronger. Confrontational questioning for builders. · GitHub


“What would not kill your code makes it stronger.”

The anti-AI. Every different software offers you solutions. Nietzschian Debugger confronts you with questions.

You paste your bug. It would not repair it. Instead, it:

  • Challenges your assumptions about what’s occurring
  • Forces you to confront the proof you are avoiding
  • Tears aside your weak reasoning till solely fact stays
  • Guides you to the “aha!” second — YOUR second, not the AI’s

AI is making builders weaker. Copy-paste from ChatGPT, ship, repeat. Nobody understands their very own code anymore. Nietzschian Debugger forges stronger builders — by means of wrestle, not shortcuts.

“He who has a why to debug can bear nearly any how.”

# Published launch (npm, v0.1.0)
npx nietzschian-debugger

# Current supply (Python 3.10+)
pip set up git+https://github.com/DilawarShafiq/nietzschian-debugger.git
nietzschian debug "your bug"

Requirements:

  • Node.js >= 20 for the npm launch, or Python >= 3.10 for the present supply
  • An Anthropic API key (BYOK — deliver your personal key)

Set your Anthropic API key:

# Linux / macOS
export ANTHROPIC_API_KEY="sk-ant-..."

# Windows (PowerShell)
$env:ANTHROPIC_API_KEY = "sk-ant-..."

# Windows (CMD)
set ANTHROPIC_API_KEY=sk-ant-...
# Start a debugging session (default: nietzsche depth)
nietzschian debug "My API returns 500 however solely on Tuesdays"

# Gentle mode — for whenever you want steering, not punishment
nietzschian debug --intensity socrates "My login endpoint fails randomly"

# Maximum depth — for seniors who need ache
nietzschian debug --intensity zarathustra "Memory leak in manufacturing"

# Point it at particular code
nietzschian debug "Auth fails in ./src/middleware/auth.ts"

Level Style Best For
socrates Warm, guiding, scaffolded questions Juniors, studying fundamentals
nietzsche Direct, confrontational, no hand-holding Daily debugging (default)
zarathustra Brutal, adversarial, hostile to weak reasoning Seniors who need actual ache

  Nietzschian Debugger v0.1.0 — depth: nietzsche

You: My login endpoint returns 403 for some customers

Nietzschian: You say "some customers." That's imprecise. What separates
             those who fail from those who do not?

You: I'm unsure, it appears random

Nietzschian: "Random" is the phrase we use after we have not appeared
             arduous sufficient. What do the server logs say for the 403
             responses? Go look. I'll wait.

You: Let me examine... oh, all of them have expired JWT tokens

Nietzschian: Now we're getting someplace. Why would some customers
             have expired tokens whereas others do not? What modified
             lately in your auth system?

You: ... oh. We modified the token TTL final week and did not
     invalidate current periods.

Nietzschian: There it's. You did not want me to inform you — you
             wanted to be compelled to look.

Session Complete — 4 inquiries to root trigger (Solved)

Your Debugging Profile:
┣ Assumption-checking    ██████████  robust
┣ Evidence-gathering     ██████░░░░  reasonable
┗ Root trigger pace       ████████░░  robust

"Man is one thing that shall be overcome."
 — Friedrich Nietzsche

Command Effect
solved or discovered it End session — you discovered the foundation trigger
I hand over Get one lifeline query, then exit
exit or give up Abandon session instantly
Ctrl+C / Ctrl+D Force give up

  • Never Gives Answers — Every response is a query. The software will NEVER inform you the repair.
  • Real Code Reading — Reference a file path and it reads YOUR precise code, not generic examples.
  • Contextual Philosophy — Nietzsche whenever you’re avoiding, Seneca when overwhelmed, Sun Tzu whenever you want technique.
  • Growth Score — Track your debugging expertise throughout periods with visible bar charts.
  • Session History — All periods saved domestically in .nietzschian/periods/ for pattern monitoring.
  • Sliding Context — Long periods do not crash; older turns are transparently summarized.

Traditional AI Nietzschian Debugger
“Here’s the repair” “What have you ever tried?”
Makes you dependent Makes you harmful
You be taught nothing You be taught all the pieces
Fast however shallow Painful however everlasting
AI will get smarter YOU get smarter

  • Junior builders who need to truly be taught, not simply copy-paste
  • Senior builders who miss the wrestle that made them good
  • Engineering managers who need their crew pondering, not simply prompting
  • Bootcamp college students constructing actual debugging instinct
  • Anyone who believes one of the best developer is a self-reliant one
# Clone and set up
git clone https://github.com/DilawarShafiq/nietzschian-debugger.git
cd nietzschian-debugger
pip set up -e ".[dev]"

# Run exams (121 exams)
pytest

# Run the CLI domestically
nietzschian debug "take a look at drawback"
  • Python >= 3.10
  • Claude API through the Anthropic SDK
  • Click for the CLI, Rich for the terminal UI
  • pytest for testing

MIT



Source link