Back to Cookbook
OpenClaw recipe

Code Brutally Honest Skeptic

A reusable, brutally honest audit of your codebase you can run any time

Run a deep, no-sycophancy audit of your entire codebase and docs, dropping the results into docs/audits as a scorched-earth report. Dry humor included, crowd-pleasing strictly forbidden.

CommunitySubmitted by ruflWork5 min
Try in KiloClawFree 7-day trial

PROMPT

Check all the docs and my codebase deeply and create in docs/audits the most complete honest audit ever. Be dry, stoic, and use dark humor — no sycophancy, no crowd-pleasing. Scan any existing audits and only carry forward what was never fixed. Count all HACKS, TODOs, FIXITs, mockups, and half-assed implementations with exact numbers. Score the project on testing and documentation quality and explain what full score requires. Research similar projects and tech stacks online (YouTube, X/Twitter, GitHub) for transparent improvement suggestions based on what others are doing better.

How It Works

check all the docs and my code base deeply and create in docs/audits folder the best and most complete of all audits ever, dry, honest, deeper than Adele rolling, stupidly stoic, humbling and with nice dry and dark humor, unleash the beast, scorch the earth.

I need the ultimate bare truth on what needs still to be better, no crowd pleasing, no sycophant traits.

Scan old audits (if existent), but don't just repeat them like a parrot on a echo chamber.

Only gather from old audits what was still not fixed or implemented.

Give me a 100% accurate number of HACKS, TODOS, FIXITS, mockups, half-assed implementations

Give me a good professional score on testing and docs and explain what is needed to achieve full score.

Give me transparent suggestions based on latest bleeding edge similar tech stack and other similar projects.

Check online for recent youtube creators or on X/Twitter, repos from github and others, on similar tech stack and other similar projects to see what we can reuse and improve from what we have.

What Others Get

A true critical audit of their code that they can reuse and run whenever they feel like.

Setup Steps

  1. Open your project in Kilo Code with the full codebase and docs accessible
  2. Check docs/audits for any existing audit files to avoid repeating fixed issues
  3. Run the prompt against your full repo — expect it to take a few minutes
  4. Review the generated audit report in docs/audits
  5. Prioritize the HACKS, TODOs, and FIXITs list for your next sprint
Tags:#automation#workflow#integration#quality-audit