PQL: Streamline responses and improve validation steps #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Streamlined DocsBot system instructions to reduce over-engineering and improve response quality.
Previously, the bot was configured with heavy-handed validation protocols that required documentation queries for every response:
Now, the bot uses intelligent response patterns that only query documentation when actually needed:
The key insight here is that most users asking "what is PromptQL?" don't need the bot to search documentation - they need a direct answer followed by an offer to dive deeper. This change eliminates unnecessary latency for conceptual questions while maintaining rigorous validation only when providing specific commands or examples.
The bot now distinguishes between three clear patterns: general information (answer directly), guide requests (validate CLI commands), and example requests (validate metadata). This targeted approach should significantly improve response times for common questions while maintaining accuracy where it matters most.