Agent skill · Databases

dolt-mcp-vcs

Universal Dolt version-control workflow. Step 0 auto-detects what kind of Dolt stack is present — every make and model (classic Dolt repo, live dolt sql-server on its ACTUAL bound port, bd embedded store, Doltgres, DoltLite single-file DB, DumboDB) — and emits a ready-to-use connection descriptor, then routes to work: DoltHub visibility diagnosis (no remote configured), the bd dolt remote add plus push fix, the JSONL throttle and rapid-write-race safe pattern, and expert agents for sync, epic-closure audits, dependency mapping, and recovery. Use when working with any Dolt database, detecting

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill dolt-mcp-vcs --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 12 KB
Bundled scripts: none
Version: 0.2.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: -Read-Task-Bash(bddoltshow:*)-Bash(bddoltremote
Requires: Designed for Claude Code. Requires bd >= 1.0.4 with a Dolt-backed workspace; the dolt-mcp-server binary on PATH enables…
Path: plugins/mcp/dolt-mcp-vcs/skills/dolt-mcp-vcs/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# dolt-mcp-vcs One skill for every make and model of Dolt: detect the flavor and mode first, then do version-control work over the beads (bd) backend and DoltHub. > Formerly **`beads-dolt`** — same plugin, renamed to its Dolt-first identity. The `beads-dolt` > install slug still resolves (a deprecated catalog alias) and `/beads-dolt` is still an accepted > trigger, so existing installs keep workin

More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the dolt-mcp-vcs skill do?

Universal Dolt version-control workflow. Step 0 auto-detects what kind of Dolt stack is present — every make and model (classic Dolt repo, live dolt sql-server on its ACTUAL bound port, bd embedded store, Doltgres, DoltLite single-file DB, DumboDB) — and emits a ready-to-use connection descriptor, then routes to work: DoltHub visibility diagnosis (no remote configured), the bd dolt remote add plus push fix, the JSONL throttle and rapid-write-race safe pattern, and expert agents for sync, epic-closure audits, dependency mapping, and recovery. Use when working with any Dolt database, detecting

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill dolt-mcp-vcs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going