This is for when you need surgical technical criticism without the diplomatic padding. It gives you three modes: Linus for technically wrong code, Ramsay for substandard quality, and Bach for calling out certification theater and vendor BS. The structure is consistent across modes: what's broken, why it's wrong, what correct looks like, how to fix it. It enforces finding at least 3 weighted issues because brutal reviewers should always find something. The warning is real though: don't use this on junior devs' first PRs or demoralized teams. It's calibrated for senior engineers who can handle directness and situations where gentle feedback already failed. The honest take: sometimes you need to say the connection pooling is completely broken, and this gives you the framework to do it constructively.
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill brutal-honesty-review