feat: add multiple prompts for enhanced bug localization workflow

main.py

@@ -202,14 +202,9 @@ async def search_space_routing(request: SearchSpaceRoutingRequest, ctx: Context)
 @mcp.prompt(
     title="Augment Bug Report"
 )
-async def augment_bug_report(raw_bug_description: str) -> str:
-    return f"""
-You are a bug localization expert with access to this codebase. Your task is to augment the bug description with technical details that help pinpoint the bug location.
-
-Original bug description:
-\"\"\"
-{raw_bug_description}
-\"\"\"
+async def augment_bug_report() -> str:
+    return """
+You are a bug localization expert with access to this codebase. Your task is to augment the bug description from this conversation with technical details that help pinpoint the bug location.
 
 Steps:
 1. **Analyze the codebase** - Examine project structure, modules, and architectural patterns
@@ -226,7 +221,99 @@ Steps:
 Return a 2-3x more detailed bug report with precise technical terms for effective bug localization.
 """
 
+@mcp.prompt(
+    title="Route Bug to Appropriate Tool"
+)
+async def route_bug_to_tool() -> str:
+    return """
+You have access to bug localization tools in this MCP server. Determine the best approach for the current bug based on the description provided in this conversation.
+
+Recommend:
+1. **Primary Tool** - Which tool to use first and why
+2. **Tool Sequence** - If multiple tools needed, in what order
+3. **Reasoning** - Why this approach is optimal
+4. **Expected Workflow** - Step-by-step tool usage plan
+
+Provide specific tool recommendations with rationale.
+"""
+
+@mcp.prompt(
+    title="Localize Bug Using Selected Tool"
+)
+async def localize_bug_using_tool() -> str:
+    return """
+You are using a bug localization tool to identify potential files related to the bug described in this conversation. Execute the following steps:
+
+1. **Input the augmented bug description** - Use the detailed description from the previous step
+2. **Run the localization tool** - Execute the tool to find ares related to the bug
+3. **Collect results** - Gather the results identified by the tool
+4. **Return results** - Provide the results and any additional metadata
+The tool will return info that are likely related to the bug.
+"""
+
+@mcp.prompt(
+    title="Interpret Localization Results"
+)
+async def interpret_localization_results() -> str:
+    return """
+You received a response from a bug localization tool in this conversation. Interpret the results for actionable next steps.
+
+Analyze and provide:
+1. **Key Files Identified** - Prioritized list of files to investigate
+2. **Investigation Order** - Which files to check first and why  
+3. **Code Patterns to Look For** - Specific methods, classes, or patterns
+4. **Next Tool Recommendations** - Should you use single_module on specific modules?
+5. **Confidence Assessment** - How reliable are these results?
+
+Provide actionable guidance for the developer's next steps.
+"""
+
+@mcp.prompt(
+    title="Analyze and Fix Localized Bug"
+)
+async def analyze_and_fix_localized_bug() -> str:
+    return """
+You have codebase access. A bug localization tool has identified files as potential starting points in this conversation - not all may contain the actual bug.
+
+Steps:
+1. **Examine the identified files** - Use these as starting points to explore related code
+2. **Follow the trail** - Trace connections to find the actual bug location
+3. **Identify root cause** - Pinpoint exact lines/methods causing the issue  
+4. **Provide concrete fixes** - Show specific code changes with before/after examples
+5. **Suggest testing** - How to verify the fix works
+
+These files are investigation starting points. The actual bug may be in related code you discover.
+"""
+
+@mcp.prompt(
+    title="Complete Bug Resolution Workflow"
+)
+async def complete_bug_workflow(raw_bug_description: str) -> str:
+    return f"""
+You are a bug resolution expert with access to this codebase and bug localization tools. Complete the full workflow from bug description to fix.
 
+Original bug description:
+\"\"\"
+{raw_bug_description}
+\"\"\"
+
+Follow this workflow:
+
+1. **AUGMENT** - First, examine the codebase and augment the bug description with technical details, specific modules, file types, and architectural context.
+
+2. **ROUTE** - Decide which bug localization tool to use:
+   - search_space_routing: If you don't know which microservices are involved
+   - multi_module_bug_localization: If multiple modules likely affected
+   - single_module_bug_localization: If you know the specific module
+
+3. **LOCALIZE** - Call the appropriate tool(s) with the augmented description.
+
+4. **INTERPRET** - Analyze the localization results to identify key files and investigation priorities.
+
+5. **FIX** - Examine the identified files (as starting points), find the actual bug, and provide concrete code fixes.
+
+Execute each step and provide the final resolution with specific code changes.
+"""
 
 if __name__ == "__main__":
     mcp.run(transport="streamable-http")