development-tools
Provides a CLI to run tests and manage background services while using sockets to prevent port collision issues.
Install
mkdir -p .claude/skills/development-tools && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4654" && unzip -o skill.zip -d .claude/skills/development-tools && rm skill.zipInstalls to .claude/skills/development-tools
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run unit tests, integration tests, and development tasks for multigresKey capabilities
- →Execute unit tests with short-circuiting to isolate logic
- →Automate background service port allocation
- →Run tests via specific package path patterns
- →Filter test execution by name or regex pattern
- →Generate verbose summaries for test debugging
How it works
The tool manages internal port pools via a local unix socket to avoid collisions during concurrent execution. It wraps standard go test commands with preset environment variables and flags to handle dependency requirements automatically.
Inputs & outputs
When to use development-tools
- →Running all unit tests for the project
- →Executing specific package integration tests
- →Managing port allocation for concurrent testing
About this skill
Development Tools
Development commands for the multigres project.
Command Structure
/mt-dev [minigres] [test-type] [args...]
The optional leading minigres qualifier runs integration tests against the
single-process Minigres topology instead of full Multigres — see "Minigres
Topology" under Integration Tests. It's a prefix, not a package name, so it
composes with any package: /mt-dev minigres integration queryserving,
and (once a package gains Minigres awareness) /mt-dev minigres integration <that-package> too, with no new alias needed per package.
For Claude Code
When executing commands:
- Always run
make buildbefore integration tests - Port pool: Before integration tests, run
scripts/portpool.sh start(idempotent, safe to call every time). Then prefix thego testcommand withMULTIGRES_PORT_POOL_ADDR=/tmp/multigres-port-pool.sockto coordinate port allocation and avoid flaky collisions. If the socket already exists (e.g. from a previous session), just set the env var — no need to restart. - Show the actual command being executed before running it
- Summarize test results (passed/failed counts, execution time)
- If tests fail, offer to show detailed output or logs
- For verbose output, provide a summary rather than dumping everything
Unit Tests
Unit tests are fast, isolated tests for individual functions and packages. They don't require external services or build artifacts.
Note: plain go test ./go/... will also traverse go/test/endtoend/...; use -short for unit-focused runs.
Command Syntax
Run all unit tests:
/mt-dev unit all
Executes: go test -short ./go/...
Run specific package:
/mt-dev unit <package-path>
Examples:
/mt-dev unit ./go/services/multipooler/...- All multipooler package tests/mt-dev unit ./go/multigateway/...- All multigateway package tests/mt-dev unit ./go/pgprotocol/...- All pgprotocol package tests
Run specific test:
/mt-dev unit <package-path> <TestName>
Examples:
/mt-dev unit ./go/services/multipooler TestConnectionPool/mt-dev unit ./go/pgprotocol TestParseQuery
Run with pattern matching:
/mt-dev unit <package-path> <TestPattern>
Examples:
/mt-dev unit ./go/services/multipooler TestConn.*- All tests starting with TestConn/mt-dev unit ./go/multigateway Test.*Route.*- All tests with "Route" in name
Common Flags
-v- Verbose output (shows all test names as they run)-race- Enable race detector (slower, catches concurrency bugs)-cover- Show coverage percentage-coverprofile=coverage.out- Generate coverage report-count=N- Run tests N times (useful for flaky test detection);-count=1also forces re-run and bypasses test cache-timeout=30s- Set timeout (default: 10m)-short- Skip long-running tests-parallel=N- Run N tests in parallel (default: GOMAXPROCS)
Examples
# Quick test run
/mt-dev unit all
# Verbose with race detection
/mt-dev unit ./go/services/multipooler/... -v -race
# Coverage report
/mt-dev unit ./go/pgprotocol/... -cover
# Test for flakiness
/mt-dev unit ./go/multigateway TestRouting -count=10
# Fast tests only
/mt-dev unit all -short
# Specific test with verbose output
/mt-dev unit ./go/services/multipooler TestConnectionPool -v
Natural Language Support
- "run unit tests" →
/mt-dev unit all - "test the multipooler package" →
/mt-dev unit ./go/services/multipooler/... - "run TestConnectionPool" →
/mt-dev unit ./go/services/multipooler TestConnectionPool - "run all unit tests with coverage" →
/mt-dev unit all -cover - "check for race conditions in multigateway" →
/mt-dev unit ./go/multigateway/... -race
Integration Tests
Integration tests are end-to-end tests that start real components (Multigateway, Multipooler, PostgreSQL) and test their interactions. These tests are slower and require building the project first.
IMPORTANT: Integration tests always run make build first.
Available Test Packages
all- Run all integration testsmultipooler- Connection pooling, pool lifecycle, connection managementmultiorch- Orchestration, failover, leader election, consensus protocolqueryserving- Query routing, execution, transaction handlinglocalprovisioner- Local cluster provisioning and setupshardsetup- Shard configuration and managementpgregresstest- PostgreSQL regression tests (opt-in, comprehensive)
Minigres Topology
Prefix any integration command with minigres to run it against the
single-process Minigres topology instead of full Multigres, e.g.
/mt-dev minigres integration queryserving. This sets
MULTIGRES_E2E_TOPOLOGY=minigres in the test environment — a qualifier on
the command, not a separate package, so it composes with whichever package
follows rather than needing its own alias.
Only queryserving and its sqllogictest/pgparity/pgproto/
postgresttests sub-packages have any Minigres awareness today —
pgregresstest, multipooler, multiorch, shardsetup, etc. read nothing
from that env var, so prefixing them with minigres is a harmless no-op
that still runs against full Multigres. Tests that inherently need a second
pooler or Multiorch (failover buffering, replica reads, cross-gateway
cancel) skip themselves under this topology; see the table in
docs/general/minigres.md.
Integration Test Command Syntax
Run all integration tests:
/mt-dev integration all
Executes: make build && go test ./go/test/endtoend/...
Run specific package:
/mt-dev integration <package-name>
Examples:
/mt-dev integration multipooler→make build && go test ./go/test/endtoend/multipooler/.../mt-dev integration multiorch→make build && go test ./go/test/endtoend/multiorch/.../mt-dev integration queryserving→make build && go test ./go/test/endtoend/queryserving/.../mt-dev minigres integration queryserving→make build && MULTIGRES_E2E_TOPOLOGY=minigres go test ./go/test/endtoend/queryserving/...
Run specific test:
/mt-dev integration <package-name> <TestName>
Examples:
/mt-dev integration multiorch TestFixReplication→make build && go test -run TestFixReplication ./go/test/endtoend/multiorch/.../mt-dev integration multipooler TestConnCache→make build && go test -run TestConnCache ./go/test/endtoend/multipooler/...
Run specific test in all packages:
/mt-dev integration all <TestName>
Example:
/mt-dev integration all TestBootstrap→make build && go test -run TestBootstrap ./go/test/endtoend/...
Run with pattern matching:
/mt-dev integration <package-name> <TestPattern>
Examples:
/mt-dev integration queryserving Test.*Transaction.*- All transaction tests/mt-dev integration multipooler TestConn.*- All connection tests
Integration Test Flags
Same flags as unit tests, plus:
-timeout=30m- Integration tests often need longer timeouts (default: 10m)-p=1- Run packages sequentially (useful if tests conflict on resources)-count=N- Run tests N times (useful to detect flakes);-count=1also forces re-run and bypasses test cache
Integration Test Examples
# Run all integration tests
/mt-dev integration all
# Test multipooler with verbose output
/mt-dev integration multipooler -v
# Test specific failure scenario
/mt-dev integration multiorch TestFixReplication
# Check for race conditions in query serving
/mt-dev integration queryserving -race
# Test for flakiness (run 10 times)
/mt-dev integration multipooler TestConnCache -count=10
# Run with extended timeout
/mt-dev integration all -timeout=45m
# Sequential execution to avoid resource conflicts
/mt-dev integration all -p=1
Integration Test Natural Language
- "run integration tests" →
/mt-dev integration all - "run multipooler tests" →
/mt-dev integration multipooler - "test multiorch TestFixReplication" →
/mt-dev integration multiorch TestFixReplication - "run all integration tests with race detector" →
/mt-dev integration all -race - "test query serving" →
/mt-dev integration queryserving - "run queryserving tests against minigres" →
/mt-dev minigres integration queryserving
Interpreting Test Results
Success Output
PASS
ok github.com/multigres/multigres/go/services/multipooler 2.456s
- All tests passed
- Shows package path and execution time
Failure Output
--- FAIL: TestConnectionPool (0.15s)
pool_test.go:45: expected 10 connections, got 8
FAIL
FAIL github.com/multigres/multigres/go/services/multipooler 2.456s
- Shows which test failed
- Shows file, line number, and failure message
- Claude should summarize: "TestConnectionPool failed in pool_test.go:45"
Build Failure
# github.com/multigres/multigres/go/services/multipooler
./connection.go:123:45: undefined: somethingMissing
FAIL github.com/multigres/multigres/go/services/multipooler [build failed]
- Compilation error before tests could run
- Claude should highlight the build error and suggest checking the code
Race Condition Detected
==================
WARNING: DATA RACE
Read at 0x00c0001a2080 by goroutine 7:
...
==================
- Race detector found a potential concurrency bug
- Claude should flag this as critical and recommend investigation
Timeout
panic: test timed out after 10m0s
- Test exceeded timeout
- Claude should suggest increasing timeout or investigating hanging test
Common Workflows
Before Committing Code
# 1. Run unit tests (fast feedback)
/mt-dev unit all
# 2. If unit tests pass, run integration tests
/mt-dev integration all
# 3. Check for race conditions
/mt-dev integration all -race
Debugging a Failing Test
# 1. Run the specific test with verbose output
/m
---
*Content truncated.*
When not to use it
- →Running non-Go project tests
- →Executing production-grade deployments or infrastructure provisioning
Prerequisites
Limitations
- →Requires existing socket from portpool script
- →Limited strictly to defined project package paths
- →Verbose output can become unreadable without summarizing
How it compares
It abstracts the environment setup and port coordination logic that would otherwise require manual script execution or port management.
Compared to similar skills
development-tools side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| development-tools (this skill) | 1 | 7mo | Review | Intermediate |
| webapp-testing | 353 | 7mo | Review | Intermediate |
| dev-browser | 53 | 8mo | Review | Intermediate |
| playwright-browser-automation | 29 | 11mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by multigres
View all by multigres →You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
dev-browser
SawyerHood
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
playwright-browser-automation
lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
windows-ui-automation
martinholovsky
Expert in Windows UI Automation (UIA) and Win32 APIs for desktop automation. Specializes in accessible, secure automation of Windows applications including element discovery, input simulation, and process interaction. HIGH-RISK skill requiring strict security controls for system access.
unity-mcp-orchestrator
CoplayDev
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
agent-browser
vercel-labs
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.