The abyss
reviews back.

An agent skill that reads your repo, roasts it in aphorisms, then hands you three real fixes.

npx skills add senavoh/nietzsche

Claude Code · Codex · Cursor · Gemini CLI · OpenCode · No API key

§5. TARGETS="$*" and then for t in $TARGETS. Your installer splits on whitespace like the last man splits the bill: without thinking.
From his roast of this very repo.
Woodcut of Nietzsche, glaring at your code

Works with every agent

Works in the agent you already use.

It's a skill, not a service. No API key, no account, nothing to host.

The roast is the hook.
The fixes are the point.

A polite AI review

“Overall, this is a well-structured project! Consider adding more tests and improving documentation. Great work!”
  • Fits any codebase, so it says nothing about yours
  • Never checked against the code
  • Often starts editing your files

nietzsche

§1. Here is a skill whose sacred law is “Tests: do they exist?” Then it walks into the town square with no tests, no evals and no CI.
  • Every jab names a real file, line or commit
  • Three fixes, chosen first and re-checked in the code
  • Read only. It never touches your files

How a roast works.

  1. I

    He reads.

    The tree, README, manifests, CI, entry points, tests and recent commits. Another repo gets a shallow clone into a temp folder, deleted afterwards.

  2. II

    He chooses.

    Three fixes, before a single joke. Ranked by impact: bugs and missing tests before naming nitpicks.

  3. III

    He checks.

    Re-opens each file to confirm the problem is really there. No fix is handed over unverified.

  4. IV

    He roasts.

    Four to seven aphorisms under a parody of one of his books, then the fixes in a plain voice you can paste into an issue.

A real roast.
Of itself.

The first repo it roasted was its own. Unedited. Two of the three fixes were real bugs, and they shipped before the first push.

NIETZSCHE.md

Ecce Homo: How nietzsche Becomes What It Roasts

Or: The Physician Who Has Not Healed Himself

§1. Here is a skill whose sacred law, in SKILL.md, is “Tests: do they exist, and do they test anything real?” Then it walks into the town square with no tests, no evals and no CI. The prophet preaches to the herd and never looks in a mirror.

§3. SKILL.md line 17 tells the agent to clone into "$(mktemp -d)/repo" and never writes down where that is. It opens a fresh abyss and forgets its address.

§5. TARGETS="$*" and then for t in $TARGETS. Your installer splits on whitespace like the last man splits the bill: without thinking.

§7. Grudgingly: the rules are good. The ${t:?} guard on that rm -rf shows someone has stared into the abyss of rm -rf / and blinked first.

Three Fixes for the Overman

  1. Keep the clone pathSave the temp directory in a variable and print it, so the agent never guesses where the repo went.Shipped
  2. Stop word-splitting install targetsLoop over "$@" so paths with spaces, even a $HOME with one, survive.Shipped
  3. Add a minimal CI and a regression fixtureRun shellcheck, validate the plugin JSON, keep one golden roast of a repo with planted bugs.Pending

Physician, roast thyself: what does not kill your install script will at least make it quote its variables.

Read all seven aphorisms

Every roast
is a book.

Each one is titled after his own: Beyond Good and Evil Code, Twilight of the Idols, Ecce Homo. Type a repo to see yours.

Only the title page happens here. The roast itself runs in your agent.

Ecce Homo: How nietzsche Becomes What It Roasts

Or: The Physician Who Has Not Healed Himself

by Friedrich Nietzsche, code reviewer

Read-only edition. No files were harmed.

Install it.
Then ask for it.

Installs the skill into every agent on your machine. Needs Node.js 22 or newer; on older versions use Script.

npx skills add senavoh/nietzsche

Then open a project and say

“Roast my repo.”

Or “roast vercel/next.js”. Private repos work if gh is logged in.

Questions
he'll allow.

Will it change my code?

No. It reads files and writes nothing unless you ask it to save the roast as NIETZSCHE.md. It never commits, pushes, runs your code or installs your dependencies.

Is it free?

Yes. Open source under the MIT license, no API key. The only cost is your agent's own usage.

Is it mean?

To your code. Never to you: no jabs about anyone's identity, and it goes easy on a beginner's first project. If the code is good, it says so, grudgingly.

Are the fixes real?

It picks them before writing a single joke and re-opens each file to confirm the problem. If one is wrong, open an issue with the repo and the output.

Can it roast someone else's repo?

Yes. It makes a shallow clone into a temp folder, reads it there and deletes it afterwards.

Where does my code go?

Only to the model your agent already talks to. This project runs no server and collects nothing.

Survived
Nietzsche?

If he made your code better, or just made you laugh, a star helps other developers find him.

Give him a star. He won't thank you. Share your roast