[discover] 1 new just-bash project(s) — 2026-05-25

[github-actions]

Weekly discovery found 1 candidates that passed all checks.
Review each one, check the entries you want to include, then comment /apply.

Candidates

• uriafranko/filesystem-sdk — Filesystem Adapters
  • POSIX-like virtual filesystem layer over files-sdk storage providers (R2, Vercel Blob, local, memory) that implements the just-bash IFileSystem interface directly
  • Confidence: 0.87 — filesystem-sdk explicitly implements just-bash's filesystem interface, provides a real install command, rich usage examples, and is clearly just-bash focused with integration documented in detail. Strong candidate for Filesystem Adapters.

Considered but skipped (13)

• boozedog/pi-codemode (Skip, 0.75) — just-bash is mentioned as one possible backend for CLI capabilities but is not central to the project's identity — it's a broader Pi extension that supports multiple backends. Fails is_subject_focused and install_command_matches_name.
• constructive-io/just-bash-test (Skip, 0.95) — The README is entirely about PostgreSQL tooling and pgpm workspaces; just-bash is a name collision. No connection to the virtual bash environment project.
• dbreunig/dspy-just-bash-interpreter (Integrations, 0.7) — While this is clearly just-bash focused (uses the Python port), the README excerpt is too minimal — no install command matching the repo name and no usage code example, failing multiple hard gates.
• devxiyang/just-bash-demo (Built With just-bash, 0.65) — This is a compelling demo built on just-bash with real code and use cases, but it lacks an install command matching the project name (it's a demo repo, not a package). Marginally relevant as a 'Built With' example but fails install_command_matches_name hard gate.
• just-buildit/just-bashit (Skip, 0.97) — This is a real shell scripting toolkit but has nothing to do with vercel-labs/just-bash. Pure name collision with 'bash' in the name.
• leif293/just-bash-lazy-sql (Skip, 0.95) — The README is essentially a copy of the canonical just-bash README (same wording, same examples, same feature list). Fails is_not_copy_of_canonical and describes_unique_value.
• MauricioPerera/agent-skills-cli (Skip, 0.72) — just-bash is used as an execution substrate but is secondary to the agent-skills spec tooling. The project is primarily about SKILL.md validation and skill-bank operations, not just-bash itself. Fails is_subject_focused.
• mesopelagique/JustBash (Ports, 0.7) — This is a genuine port to the 4D language, but the README has no usage example and no install command, failing two hard gates. Too sparse to include confidently.
• mwolting/context-fs (Skip, 0.78) — just-bash is one of several packages in this broader framework (@context-fs/just-bash), but the project's identity is the context-fs ecosystem as a whole. Fails is_subject_focused since just-bash is just one adapter among many targets.
• nicoalbanese/ai-sdk-memory-just-bash (Skip, 0.72) — just-bash is used in one of three approaches in this example repo, making it peripheral rather than central to the project's identity. Fails is_subject_focused.
• Pibomeister/just-bash-vercel-ai-sdk-elements (Skip, 0.68) — just-bash is one of several major components in a broader production stack. While prominently featured, the project's identity is a full-stack blueprint rather than a just-bash-focused project. Fails is_subject_focused.
• tobowers/minimal-just-bash-failure (Skip, 0.92) — This is a bug reproduction repo, not a library, integration, or project building on just-bash. It has no unique value to add to an awesome list — it's a temporary debugging artifact.
• vercel-labs/wterm (Skip, 0.78) — wterm is a full terminal emulator framework where just-bash is one of seven packages. The project's identity is the terminal emulator, not just-bash. Fails is_subject_focused despite the @wterm/just-bash subpackage being genuinely interesting.

---

Generated by .github/workflows/discover.yml on 2026-05-25.
LLM cost: $0.1047 — openrouter/anthropic/claude-sonnet-4.6, 21830 in / 2686 out tokens.
Check the entries you want, comment /apply, and the workflow will edit the README and mark this PR as ready.