pride

A contrarian code review examines git diffs to surface overlooked defects, duplicate fixes, and unsafe shell usage. It enforces skeptical, evidence-backed findings with concrete remediation steps instead of assuming passing checks mean the code is safe.

Confidence laundering is when generated prose masks unsupported assertions or over-claims as factual. You check for it by applying a skeptical review to research briefs and documentation, demanding explicit evidence and flagging misleading claims before publication.

Yes, you can review uncommitted changes and generated media captions together. The inspection process collects diffs and artefact text simultaneously, evaluating mixed code and narrative outputs to find both type smells and unsourced claims.

Reviewing a branch before pushing involves running a skeptical inspection on the current git range. This surfaces race conditions, type smells, and unsafe shell usage, returning per-file findings with concrete fixes to apply before pushing.

Automated quality assurance often misses misleading claims in generated research briefs because it checks for passing tests rather than factual accuracy. A contrarian review process explicitly audits prose for unsourced claims and confidence laundering that automated checks overlook.

Automated checks often adopt a green-is-good mindset, missing subtle defects like race conditions and confidence laundering. A contrarian review is limited by token-aware truncation for large payloads, but it enforces the evidence-backed findings that automated checks lack.