What problem does it solve? Traditional Minecraft mod development forces a merge-test-rollback cycle because features can only be tested after merging into the main workspace. This Skill replaces that loop with Git worktrees plus mcdev-tools, letting you test feature workspaces directly without any git merge until the feature is confirmed. ## Core Features & Use Cases - Parallel Feature Workspaces: Creates isolated Git worktrees with feature branches, copying IDE configuration and committing pending main-workspace changes first for a stable baseline. - Direct Testing Without Merge: Switches the .mcdev.json included_mod_dirs path so mcdev-tools loads the feature workspace code directly, with optional AI-assisted testing through the mcdk_dev MCP server (screenshots, code execution, log reading, hot reload). - Safe Integration & Cleanup: Merges only after tests pass, restores .mcdev.json to main-workspace paths before merging to avoid path pollution, and requires user confirmation before removing worktrees or branches. - Use Case: You are building a new gameplay feature while another feature is in progress. The Skill creates a separate worktree, points mcdev-tools at it, lets you test and fix in place, then merges into main only after you confirm the feature works. ## Quick Start Ask the assistant to start a new feature using the parallel worktree workflow and tell it whether you want to work in the main workspace or a new feature workspace.
