brutal-honesty-review

Deliver unvarnished technical criticism on code and testing practices.

436|78|Updated Sep 11, 2025

Search Tags:#quality #honesty #code-review #critique #bs-detection

Ready to run

npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill brutal-honesty-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brutal-honesty-review
Source: https://github.com/proffesor-for-testing/agentic-qe/tree/main/.claude/skills/brutal-honesty-review
Command: npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill brutal-honesty-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill delivers sharp, actionable, no-nonsense technical critique to fast-track improvements in code, tests, and processes.

Core Features & Use Cases

Mode Switching: Linus (technical), Ramsay (standards), Bach (BS detection).
Structured Output: Clear problem statements, root causes, and fixes.
Action‑Oriented: Roadmaps and checks to prevent recurrence.

Quick Start

Run a brutal honesty review on a recent PR to surface concrete improvements.

Frequently Asked Questions about brutal-honesty-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I conduct a code review that identifies real problems instead of surface-level issues?▼

Brutal honesty review delivers unvarnished technical criticism on code and testing practices by applying structured templates and mode-specific critique. It surfaces root causes and actionable fixes rather than cosmetic feedback, fast-tracking concrete improvements in architecture, bugs, and process quality.

What's the best way to evaluate vendor claims and detect technical BS in architecture decisions?▼

The BS-detection mode (Bach) applies critical evaluation to vendor claims and architectural assertions. It structures your critique around evidence gaps and practical trade-offs, helping you separate marketing from technical merit in infrastructure and framework choices.

How do I give code critique that leads to actionable fixes, not just complaints?▼

Brutal honesty review pairs problem statements with root causes and concrete remediation steps. It provides roadmaps and preventive checks so teams implement fixes rather than dismiss feedback as subjective criticism.

Can I switch between different critique styles for different code review contexts?▼

Yes. Three modes let you tailor critique depth: Linus (technical depth), Ramsay (standards and practices), and Bach (BS detection). Mode switching addresses senior engineers, repeated mistakes, critical bugs, and external claims with the right critique intensity.

What should I review with this approach—just code, or testing and processes too?▼

Brutal honesty review covers code, testing practices, and architectural processes. Structured templates guide assessment of all three, making it suitable for architectural reviews, test-quality audits, and process improvements alongside PR critique.

Does this work for catching repeated architectural mistakes across a codebase?▼

Yes. The Skill targets repeated architectural mistakes alongside critical bugs. Structured output and actionable roadmaps help teams identify systemic patterns and implement preventive checks to break recurrence cycles.