github-issue-worktree vs DEEPBOM
github-issue-worktree is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
github-issue-worktree is a plugin bundle for AI coding tools published by gabrielkoerich. No marketplace we read lists it any more. DEEPBOM is an MCP server published by JunHwan-Kwon. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  DEEPBOM | |
|---|---|---|
| Community marketplace gabrielkoerich/skills | Removed on 2026-10-21 Version: not stated Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.5.0 Downloads/month (npm): 2 449 Downloads/week (npm): 277 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.5.0 Downloads/month (npm): 2 449 Downloads/week (npm): 277 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | github-issue-worktreeno longer listed · | DEEPBOM |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 6 | 2 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/gabrielkoerich/skills | github.com/junhwan-kwon/deepbom |
| Changes in the last 7 days (differs) | 5 | 2 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of github-issue-worktree
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
GitHub workflow: issues, PRs, worktrees, sub-issues
-
Effortless git worktrees for parallel development with automatic environment setup
-
Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.
-
Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.
-
Take GitHub issues to reviewed pull requests through isolated worktrees, tests, and explicit merge gates.
-
A band above the prompt with the git worktrees of the current repo: branch, uncommitted changes, and the count against a limit of 10.
What each says it does
github-issue-worktree
Manage an isolated worktree per GitHub issue. Register the branch with `gh issue develop`, then create, list, and remove the worktree with `git cow` only, by following the git-worktrees skill. The default directory is `~/.worktrees/<project>/`. Use it when the user explicitly asks to work on a GitHub issue.
DEEPBOM
Browser-local and CLI static evidence for deployed AI model artifacts.
How to run each
github-issue-worktree
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
DEEPBOM As a remote MCP server
claude mcp add --transport http deepbom https://deepbom.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only DEEPBOM has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: github-issue-worktree · What it can do: DEEPBOM · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.