WeSearch
Vibes vs. Evidence: What delivers AI code review quality

Vibes vs. Evidence: What delivers AI code review quality

·1 min read · 0 reactions · 0 comments · 1 view
More from Github ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

Research indicates that using a structured harness for AI code review significantly improves the detection of verified bugs compared to single-prompt methods. In 39 out of 42 comparisons, harness-based approaches like Compound Engineering and metareview outperformed one-shot prompting with the same model. However, this increased accuracy comes at the cost of approximately ten times more token usage and a higher volume of unsupported findings requiring manual verification.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 5,917 of its stories.

Original article
Github
Read full at Github →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGithub
Canonical URLhttps://dsifry.github.io/harnesseval/
Publication timeTue, 22 Sep 2026 02:12:35 +0000
Retrieval time2026-09-22T02:58:49.462Z
Last seen2026-09-22T02:58:49.462Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterYSRqer2-HmED · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Finding · harness 1.6× Same model, add a harness: 1.6× verified bugs found by AI code review A harness runs the model as a team of specialist reviewers instead of a single prompt. Compound Engineering and metareview beat the same model’s one-shot prompt in 39 of 42 comparisons. GLM-5.3 running metareview at low effort gained 2.1×. The price: about 10× the tokens, and more unsupported findings to check. AI code review: same model, add a harness (Compound Engineering or metareview) and it found 1.6× the verified bugs, beating one-shot prompting in 39 of 42 same-model comparisons at about 10× the tokens. Data and method:

Excerpt limited to ~120 words for fair-use compliance. The full article is at Github.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Github