Use when cutting a new gdevelop-mcp release. Bumps the version, finalizes CHANGELOG, tags the commit, and (optionally) pushes/publishes.
Run a structural audit of the gdevelop-mcp repo before tagging a release. Checks file sizes, README↔code sync, test coverage, deps freshness. Reports concisely without auto-fixing.
Use after adding, renaming, or removing an MCP tool or prompt. Ensures README, CHANGELOG, and version numbers stay in sync with the actual code surface. The hard rule from .claude/rules/maintenance.md.
Use when adding a new MCP prompt (slash command) to the gdevelop-mcp server. Prompts inject a guided workflow message — they don't run code directly.
Use when adding a new tool to the gdevelop-mcp server. Walks through the file/test/registration changes required.
Use when adding tests for new or existing code in gdevelop-mcp. Tests use vitest, live in test/, and follow the safety-first priorities laid out in .claude/rules/testing.md.
Use when the gdevelop-mcp server misbehaves — tools missing, prompts not exposed, JSON-RPC errors, or unexpected responses.