go-dev-mcp

This skill should be used when the user asks to verify, audit, or review that the dq-based documentation parsers still work against the live site. Trigger phrases include "verify doc parsing", "check pkg.go.dev parsing still works", "is our godoc/rustdoc/pydoc parser still correct", "check for doc site drift", "review our dq-based parsing", "browse docs.rs and review parsing", "did pkg.go.dev change its HTML". It uses the browser-sandbox MCP tool to browse the live documentation site and compare the real DOM against the CSS selectors the parser depends on, flagging drift and robustness gaps.

This skill should be used when the user asks to add support for a new documentation site or integrate a new doc source. Trigger phrases include "add Java docs support", "integrate Node.js docs", "add MDN support", "new documentation site integration", "add docs for Ruby", "support reading docs from [site]". It guides implementing the 3-tool pattern (search/read/search_within) using the dq HTML document query package, following the proven pattern from the existing godoc (pkg.go.dev), rustdoc (docs.rs), and pydoc (docs.python.org) integrations.