Build and verify the Coding Tools MCP Windows portable release ZIP. Use when asked to compile, rebuild, package, or troubleshoot a portable desktop executable, especially when a packaged app opens localhost:1420 or reports ERRCONNECTIONREFUSED.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?".
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
Drives Coding Tools MCP desktop development to completion against old/ parity. Use when the user invokes /goal, says 开始开发直到完成, or asks to finish the rust-desktop-client spec with shared MCP/Actions tool core aligned to old/.
Build, verify, version, tag, and package the Coding Tools MCP Node Agent as two Windows x64 portable ZIP editions: bundled-node with embedded Node.js and system-node without Node.js. Use when creating or reviewing Node Agent portable releases, enforcing release tag-to-commit provenance, changing launchers or archive…