Skip to content

Add Alexs7zzh/hunk-extensions to hunk-extension marketplace - #1024

Open
benvinegar wants to merge 1 commit into
mainfrom
claude/funny-keller-o94gge
Open

Add Alexs7zzh/hunk-extensions to hunk-extension marketplace#1024
benvinegar wants to merge 1 commit into
mainfrom
claude/funny-keller-o94gge

Conversation

@benvinegar

Copy link
Copy Markdown
Member

Summary

Daily scan of the hunk-extension GitHub topic found one newly discovered repository in the last 24 hours that isn't yet in the marketplace catalog:

  • Alexs7zzh/hunk-extensions — created and pushed 2026-09-07, tagged hunk-extension, MIT licensed. Description: "Hunk extensions, including Plastic SCM support."

This adds it to website/src/data/extensions.ts in alphabetical order (sorted right after Hunk's own listings, ahead of astwys/*), plus an empty Changeset per repo convention for a maintenance-only change.

⚠️ Needs maintainer verification before merge: this session's GitHub access is scoped to modem-dev/hunk only, so I could not read the extension's manifest, README, or source directly (and GitHub code search hasn't indexed the repo yet, being only hours old). The entry's summary and categories: ["VCS backend"] are inferred from the repo description alone. version: "0.1.0" and apiVersion: 16 are placeholders based on the catalog's typical/most-recent values — please confirm both against the extension's actual manifest (hunk.apiVersion, version) before merging, and adjust the summary/category if the repo bundles more than the one Plastic SCM extension its name suggests.

Two other repos matched the topic search but were excluded:

  • jacegodk/hunk-viewed and victor-software-house/hunk-history were updated in the last 24h but are already listed.
  • modem-dev/hunk-opencode is not yet listed but was last updated 2026-09-05 (outside the 24h window), so left for a future scan.

Test plan

  • bun run typecheck passes
  • bunx oxfmt --check / bunx oxlint clean on the changed file
  • Maintainer confirms version/apiVersion/categories against the actual extension manifest

🤖 Generated with Claude Code

https://claude.ai/code/session_014Z8N7p1C4ofqabJymLSorz


Generated by Claude Code

Discovered via the daily hunk-extension topic scan: created and pushed
today, tagged hunk-extension, not yet in the catalog.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014Z8N7p1C4ofqabJymLSorz
@vercel

vercel Bot commented Sep 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
hunk-web Building Building Preview Sep 7, 2026 1:10pm UTC

Request Review

@greptile-apps

greptile-apps Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds Alexs7zzh/hunk-extensions to the extension marketplace and includes the conventional empty changeset for a maintenance-only update.

  • Adds marketplace display, search, filtering, version, and API metadata for the extension.
  • The externally sourced metadata still requires verification against the extension's manifest and entry file.
  • The empty changeset follows the repository's documented convention.

Confidence Score: 4/5

The change is non-blocking structurally, but its marketplace metadata should be verified before merge to avoid publishing unsupported compatibility and classification claims.

The empty changeset and catalog shape are valid, but several user-visible fields were populated from inference or placeholders rather than the extension source.

Files Needing Attention: website/src/data/extensions.ts

Important Files Changed

Filename Overview
website/src/data/extensions.ts Adds a new marketplace listing whose manifest-derived metadata has not yet been verified.
.changeset/marketplace-new-extension-sept7.md Adds a valid empty changeset for a maintenance-only catalog update.
Prompt To Fix All With AI
### Issue 1
website/src/data/extensions.ts:99-101
**Unverified marketplace metadata**

The catalog contract says these fields mirror the extension manifest, but `version` and `apiVersion` are explicitly placeholders, while the category was inferred without inspecting the entry file. These values are displayed and used for marketplace search and filtering, so publishing them without verification can misstate the available release, API compatibility, and extension classification. Please verify them against the extension source before adding the listing.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "Add Alexs7zzh/hunk-extensions to hunk-ex..." | Re-trigger Greptile

Comment on lines +99 to +101
categories: ["VCS backend"],
version: "0.1.0",
apiVersion: 16,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Unverified marketplace metadata

The catalog contract says these fields mirror the extension manifest, but version and apiVersion are explicitly placeholders, while the category was inferred without inspecting the entry file. These values are displayed and used for marketplace search and filtering, so publishing them without verification can misstate the available release, API compatibility, and extension classification. Please verify them against the extension source before adding the listing.

Prompt To Fix With AI
This is a comment left during a code review.
Path: website/src/data/extensions.ts
Line: 99-101

Comment:
**Unverified marketplace metadata**

The catalog contract says these fields mirror the extension manifest, but `version` and `apiVersion` are explicitly placeholders, while the category was inferred without inspecting the entry file. These values are displayed and used for marketplace search and filtering, so publishing them without verification can misstate the available release, API compatibility, and extension classification. Please verify them against the extension source before adding the listing.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants