Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/mcp/dolt-mcp-vcs/skills/dolt-mcp-vcs

dolt-mcp-vcs

Verified

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 a Dolt flavor, connecting to a Dolt store, when beads are not showing in DoltHub, taming dolt server sprawl, auditing bead epics, or recovering from a bd or Dolt incident. Trigger with "/dolt-mcp-vcs", "/beads-dolt" (the former name, still accepted), "what kind of dolt is this", "my beads aren't showing in DoltHub", or "audit my bead epics".

FileKindSize
SKILL.mdskill md12.5 KB
eval.yamlconfig4.5 KB
references/connection-descriptor-and-profiles.mdmarkdown4.9 KB
references/dolt-internals.mdmarkdown2.0 KB
safety-eval.yamlconfig5.9 KB

references/dolt-internals.md

View on GitHub
# beads + Dolt — where to get the current truth (no frozen snapshot)

This plugin keeps **no baked copy** of beads' or Dolt's internals. A hand-copied
snapshot goes stale the moment upstream ships a release and silently lies in
between. Every agent in this plugin instead **forks into its own context, fetches
the current facts from the sources below, and reports back** — so the answer is
always correct for the *installed* version, never a guess from memory.

This file is only a directory of authoritative sources + the live commands to read
them. It contains **no behavioral claims** on purpose.

## Authority order (higher wins on any conflict)

1. **The installed binary** — current to exactly what's running, by definition:
   - `bd --help`, `bd <cmd> --help` — e.g. `bd dolt --help`, `bd init --help`, `bd backup --help`, `bd config --help`
   - `bd prime` — live AI workflow context
   - `bd dolt show` — this workspace's live database, host, port, mode
   - `bd config list` / `bd config get <key>` — the effective config
   - Live data model — introspect, never assume: `SHOW TABLES`, `information_schema.columns`, `SHOW CREATE TABLE <t>` (via the Dolt MCP)

2. **Official upstream docs** (maintained with the code) — `curl` the raw files or read the site:
   - beads repo: <https://github.com/gastownhall/beads> — `docs/DOLT-BACKEND.md`, `docs/DOLT.md`, `docs/CONFIG.md`, `docs/CLI_REFERENCE.md`, `docs/INTERNALS.md`, `docs/FEDERATION-SETUP.md`
     (raw: `https://raw.githubusercontent.com/gastownhall/beads/main/docs/<FILE>.md`)
   - beads docs site: <https://gastownhall.github.io/beads/>
   - Dolt: <https://docs.dolthub.com> · <https://github.com/dolthub/dolt>
   - Dolt MCP: <https://github.com/dolthub/dolt-mcp>

## How agents use this

Every agent here is told: **do not assert version-specific behavior from memory or
any bundled text.** Fetch it live — run the relevant `bd … --help`, `curl` the
matching official doc, or introspect the live schema — then answer from what you
just read, and name the source. The installed binary is the tie-breaker.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall