WeSearch

Show HN: Vestige - Splits large AI diffs into reviewable chunks

·3 min read · 0 reactions · 0 comments · 66 views
Show HN: Vestige - Splits large AI diffs into reviewable chunks
TL;DR · WeSearch summary

Vestige Understand this change and what it will break, so you can push it with confidence. Vestige makes AI-generated diffs reviewable before they're pushed. When an LLM changes a lot of code at once, Vestige answers three questions fast: Where do I start? — entry points and a guided reading order for the change.

Key facts
About this source

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

Original article
Visualstudio
Read full at Visualstudio →

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 publisherVisualstudio
Canonical URLhttps://marketplace.visualstudio.com/items?itemName=Vestige.vestige-vscode-extension
Publication timeMon, 20 Jul 2026 15:25:13 +0000
Retrieval time2026-07-20T15:53:38.970Z
Last seen2026-07-20T15:53:38.970Z
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.
ClusterwmLFH69MmKiW
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

Vestige Understand this change and what it will break, so you can push it with confidence. Vestige makes AI-generated diffs reviewable before they're pushed. When an LLM changes a lot of code at once, Vestige answers three questions fast: Where do I start? — entry points and a guided reading order for the change. What could this affect? — the blast radius: everything the change can reach or break. What did this code do before? — the surrounding context, without re-deriving it. How a review works Open a folder. Vestige scans and parses it locally — no LLM calls — to build a call graph and a file-dependency graph. Read the graphs. Click the Vestige icon in the activity bar, or run Vestige: Open Graph, for two tabs on one panel: Repo Graph (function calls) and Feature (feature clusters).

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

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

Discussion

0 comments

More from Visualstudio