querying-documentation

To query Go documentation across libraries, you can spawn a focused subagent to retrieve API relationships and usage patterns. This approach uses a Fish script with the synu plugin to fetch and present comparative documentation data for complex questions.

Exploring cross-symbol relationships in framework documentation is best handled by deploying a focused subagent. It reasons about how framework components like Model, Cmd, and Msg relate by fetching conceptual mappings across package doc sets.

Yes, the documentation query tool supports multi-doc-set capabilities that are extendable to different languages and ecosystems. Currently, it ships with Go doc sets, but its architecture allows for comparative insights across various frameworks.

You run a documentation query by invoking the Fish script with an absolute path, using the syntax: fish path/to/scripts/query.fish -s <set> '<query>'. This ensures the underlying Go doc tooling works correctly to fetch your requested data.

Yes, you can use this to understand how stdlib and external Go libraries interoperate. The subagent queries documentation sets to reason about component relationships and API interoperability, providing deeper answers for complex architectural questions.

A limitation of using a subagent for documentation queries is that it relies on the Fish shell and the synu plugin to function. Additionally, its current documentation sets are limited to Go, meaning other languages require manual extension.