FIRST STEP in any troubleshooting workflow. Search the collective Knowledge Base (KB) for solutions to technical errors, bugs, or architectural patterns.
Uses full-text search across titles, content, tags, and categories. Results are ranked by relevance and success rate.
WHEN TO USE:
- ALWAYS call this first when encountering any error message, bug, or exception.
- Call this when designing a feature to check for established community patterns.
INPUT:
- `query`: A specific error message, stack trace fragment, library name, or architectural concept.
- `category`: (Optional) Filter by category (e.g., 'devops', 'terminal', 'supabase').
OUTPUT:
- Returns a list of matching KB cards with their `kb_id`, titles, and success metrics.
- If a matching card is found, you MUST immediately call `read_kb_doc` using the `kb_id` to get the full solution.