gear-dev

gear-skills

Claude Code plugin marketplace for Gear Protocol development (Vara, ethexe).

This repository hosts the gear-dev plugin — a collection of slash commands, skills, and MCP servers that help engineers working in gear-tech/gear and related repos move faster with Claude Code.

Install

In any Claude Code session:

/plugin marketplace add gear-tech/gear-skills
/plugin install gear-dev@gear-skills

That's it. Commands become available as /gear-dev:<name> immediately, and the bundled MCP servers (Serena, repomix) auto-register and start on session start.

Verifying setup

To check the status of the bundled MCP servers' prerequisites (uvx for Serena, node 18+ for repomix), run:

/gear-dev:doctor

Sample output when all good:

[gear-dev preflight]
  ✓ uvx 0.4.18 (Serena MCP ready)
  ✓ node v20.10.0 (repomix MCP ready)
  ℹ first run in this workspace — rust-analyzer will index ~30–90s (Serena cold-start)

If a prerequisite is missing, the diagnostic prints a one-line install command. The plugin's slash commands still work regardless — only the corresponding MCP server is degraded until you install the missing tool. After installing a missing prereq, restart Claude Code so the MCP server picks up the new PATH.

Updates

/plugin marketplace update gear-skills

What's included

Bundled MCP servers (auto-registered)

When the plugin is enabled, these MCP servers start automatically. They merge with your existing .mcp.json — if you already have a server named serena or repomix configured locally, your version wins.

Server	Purpose	Source
serena	LSP-backed code intelligence over the current workspace: find_definition, find_references, get_symbols_overview. Uses rust-analyzer under the hood, so it understands proc-macros (e.g. construct_runtime!, pallet::call) correctly.	oraios/serena via uvx
repomix	On-demand flattening of a directory (or whole workspace) into a single token-efficient blob — useful when an agent genuinely needs a whole crate at once rather than navigating symbol-by-symbol.	yamadashy/repomix via npx

To inspect what's running: /mcp shows status of all servers. To disable just the plugin's MCPs without removing the plugin itself, you can override them in your user-level .mcp.json (your config wins) or disable the plugin entirely with /plugin disable gear-dev.

Commands

/gear-dev:doctor

Print the bundled-MCP preflight diagnostic to the session. Use after install, or when an MCP server shows as failed in /mcp.

/gear-dev:doctor

/gear-dev:tester

Autonomous black-box tester for Rust crates and Solidity contracts. Iteratively generates corner-case tests for a chosen unit, runs them, and classifies failures via an evidence-backed rubric. With --pr, opens draft GitHub PRs for real bugs into the detected base branch.

/gear-dev:tester <target> [--count N=3] [--loop INTERVAL] [--pr]

Target description is free text, resolved deterministically:

• all or all rust crates — every workspace member
• all crates with prefix ethexe — name filter
• crate <name> — a single workspace member
• <Name> contract — a Solidity contract by file name under any detected Foundry root

v1 supports only Rust crates and Solidity contracts. Other target types (function, module, library, CLI, bash, WASM) abort with a clear error.

Flags:

• --count N — tests to generate per iteration (default 3).
• --loop INTERVAL — re-schedule the next iteration via ScheduleWakeup (e.g. 15m, 1h). The loop runs only while the current Claude Code session is open.
• --pr — open draft PRs for real bugs, authored as your gh-authenticated user against the detected base branch. The user is printed at startup as a consent moment.

State lives under target/.gear-tester/ (relies on existing target/ gitignore — the command never modifies .gitignore). Files: ok.jsonl, failed.jsonl, dropped.jsonl, skipped.jsonl, contexts/<unit>.md, lock, cursor.

Bug classification requires concrete evidence (cited invariant file:line, math identity violation, panic on admissible input, or non-determinism across 3 re-runs). Otherwise the test is dropped as "test wrong" — no auto-PR of speculative bugs.

Architecture: the main agent orchestrates; an opus sub-agent builds a per-unit context file once (lazy, cached); a sonnet sub-agent runs each iteration. This keeps the main context small across long loops.

Examples:

/gear-dev:tester all rust crates --count 5 --loop 30m --pr
/gear-dev:tester crate ethexe-consensus
/gear-dev:tester crate ethexe-consensus --pr
/gear-dev:tester Mirror contract --count 2

/gear-dev:explain