search-fixes

name	search-fixes
description	Search the knowledge base for known fixes related to test failures
user-invocable	true

Search Fixes

Search the houston knowledge base for previously verified fixes that match current test failures.

Usage

/search-fixes <query-or-context-file>

• Pass a search query string to search for a specific error
• Pass a context file path to automatically search for all failures in that file

Examples:

• /search-fixes "NoSuchElementException Recommendations tab"
• /search-fixes "422 Unprocessable Entity"
• /search-fixes resources/analysis/proton_ipv4_sat-stream-rhel9-Insights-Advisor/35/context.md

Instructions

Option A: Direct search query

If the argument is a plain string (not a file path), run:

houston search "<query>" 2>&1

Print the results to the user.

Option B: Search from context file

If the argument is a path to a context file (ends in .md and exists on disk):

1. Read the context file to extract failure information (error types, exception messages, test names).

2. For each unique error pattern, run a search:

houston search "<error-pattern>" 2>&1

Good search queries to extract from failures:

• The exception class (e.g. NoSuchElementException)
• Key parts of the error message (e.g. Recommendations tab)
• The test name (e.g. test_iop_recommendations_host_details_e2e)
• The CaseComponent (e.g. Insights-Advisor)

3. Summarize the results:

• Which failures have known fixes in the knowledge base
• Which failures are new (no prior fixes found)
• Any relevant past fixes that might inform the current analysis

Recording fixes

Remind the user that they can record working fixes to grow the knowledge base:

houston feedback <recommendation-id> --worked