Add reef as external plugin (git-subdir)

[eunji-jessi-jung]

Hi — I built a Claude Code plugin called reef and would love to have it listed in your marketplace as an external plugin via git-subdir.

What it does

Structured knowledge wiki generator for codebases. Auto-discovers services, APIs, schemas, and cross-system contracts, then deepens through guided Q&A. Obsidian-native, local-first.

What's in it

• 12 skills: init, snorkel, source, scuba, deep, artifact, update, lint, health, feed, test, help
• 1 agent: reef-navigator (read-only artifact queries)
• Backend: Python script (reef.py) for indexing, manifests, linting, diffing
• License: Apache-2.0
• Dependencies: Python + PyYAML

Links

• Plugin repo: https://github.com/eunji-jessi-jung/reef
• Demo (Supabase): https://github.com/eunji-jessi-jung/supabase-reef — 5 repos, 28-run benchmark across 2 models
• Benchmark report: https://github.com/eunji-jessi-jung/supabase-reef/blob/main/reef-benchmark-report.md

Suggested marketplace.json entry

{
  "name": "reef",
  "source": {
    "source": "git-subdir",
    "url": "https://github.com/eunji-jessi-jung/reef.git",
    "path": "."
  },
  "description": "Structured knowledge wiki generator for codebases. Auto-discovers services, APIs, schemas, and cross-system contracts, then deepens through guided Q&A. Obsidian-native, local-first.",
  "version": "1.0.0",
  "category": "productivity"
}

Happy to adjust anything to fit your conventions. The plugin passes claude plugin validate . cleanly.

[wshobson]

Thanks for the detailed submission, Eunji. Took a look at the repo and the plugin itself looks well-engineered:

• .claude-plugin/plugin.json is well-formed; structure matches the claim (12 skills, 1 agent, Apache-2.0).
• scripts/reef.py (~2.3k lines) uses clean patterns — argparse, structured JSON I/O, no eval/exec/shell=True, and the subprocess calls are git invocations with argument lists rather than shell-quoted strings. No injection concerns spotted on a first pass.
• git-subdir shape in your suggested entry matches the pattern already used for qa-orchestra.

What's giving me pause is timing rather than quality: the repo is 11 days old, 1.0.0 just shipped, no stars/forks yet, and git-subdir means users pull whatever the upstream pushes — there's no review gate on subsequent updates. For brand-new plugins I'd rather see a bit of soak time and a few real users before listing it in the marketplace, where it inherits a lot of trust by association.

Two paths from here that I'd be comfortable with:

1. Defer the listing for ~30 days, give the plugin a chance to accumulate usage signal and any post-1.0 fixes, then revisit. Happy to add it then.
2. List it now but pin to a specific tag (rather than tracking the default branch) so users get a known-good snapshot. Would need to check whether the marketplace's git-subdir handler supports tag pinning — qa-orchestra doesn't pin, so I'd want to confirm before promising it.

Which would you prefer? And if (2), would you be willing to cut tagged releases on a regular cadence?

Either way, the benchmark on supabase-reef is a nice piece of evidence — that kind of empirical validation is rare and appreciated.

[wshobson]

Bumping this — happy to move forward on either path when you have a preference. The ~30-day soak window from your initial submission lands around 2026-05-16, so we're not far off if option (1) appeals.

If we go with option (2), I'd need to confirm the marketplace's git-subdir handler supports tag pinning before promising it (Anasss/qa-orchestra is the only existing external plugin and it tracks the default branch, so this would be a first). Either way, knowing your preference is the unblocker.

[eunji-jessi-jung]

Thank you for kind reply. I'll go with optionn (1).