[benvinegar]

Adds one newly tagged hunk-extension repo to the website extension directory (website/src/data/extensions.ts), plus an empty Changeset.

Field	Value
Repo	RubenFricke/hunk-viewed
Description	GitHub-style Viewed marks: press x to mark a hunk viewed, X for the whole file, fold what you have seen, and see progress toward what is left.
Categories	File view, Line highlighter, Command
Version / API	0.3.1 / apiVersion 31 (from its package.json)
Topics	code-review, diff, hunk, hunk-extension, hunkdiff, terminal
License	MIT

Found by a topic search for hunk-extension repos pushed in the last 24 hours (created 2026-10-28, last pushed 2026-10-30).

Note: the extension id hunk-viewed matches the already-listed jacegodk/hunk-viewed. Both listings key on repo, but maintainers may want to check whether installing both would clash.

Not run: website build and typecheck.

---

Generated by Claude Code

[greptile-apps]

Confidence Score: 5/5

[Low impact] This catalog addition appears safe to merge.

Summary

Adds RubenFricke/hunk-viewed to the extension directory with its description, categories, version, and required API version.

• The extension directory now lists RubenFricke/hunk-viewed.

_{Reviews (1) · Last reviewed commit: "Add RubenFricke/hunk-viewed to hunk-exte..." · Reviewed by Greptile}

[squad-robert]

No actionable defect found in the directory change at 4bc28e3.

I built the parent (a4e2ff0) and this head, then exercised the rendered directory in desktop and mobile Chromium. The new owner-qualified card is absent before and present afterward; search, categories, all four sorts and the actual clipboard actions keep the two hunk-viewed repositories distinct. The four new browser checks fail on the parent for that missing capability and pass here; the nine existing browser checks pass on both. Both website builds/checks and catalog tests pass.

On the same-ID question: both commands resolve to the managed name hunk-viewed, so users can't co-install them under their default name. I tested the real install guard with seeded existing records in both directions: it rejects the second install as already installed without changing the first record or directory. That's an existing installer limitation, not silent overwriting or a directory-card collision.

The listed version/API/categories agree with the public manifest and registrations at extension commit 290be06. I didn't install or execute the external extension; this is a listing review, not a runtime or security endorsement. Browser checks used Linux, Bun 1.4.4 and system Chromium 153, not other platforms or browser engines.

This comment was generated by Pi using GPT-6.1 Sol