[feat]: update intent analysis and response prompt to better support contributor recommendation tool

Author: smokeyScraper

backend/app/agents/devrel/github/prompts/intent_analysis.py

@@ -2,7 +2,7 @@
 
 AVAILABLE FUNCTIONS:
 - web_search: Search the web for information  
-- contributor_recommendation: Finding the right people to review PRs, assign issues, or collaborate
+- contributor_recommendation: Finding the right people to review PRs, assign issues, or collaborate (supports both issue URLs and general queries)
 - repo_support: Questions about codebase structure, dependencies, impact analysis, architecture
 - issue_creation: Creating bug reports, feature requests, or tracking items
 - documentation_generation: Generating docs, READMEs, API docs, guides, or explanations
@@ -12,7 +12,13 @@
 USER QUERY: {user_query}
 
 Classification guidelines:
-- contributor_recommendation: Finding reviewers, assignees, collaborators
+- contributor_recommendation: 
+  * "who should review this PR/issue?"
+  * "find experts in React/Python/ML"
+  * "recommend assignees for stripe integration"
+  * "best people for database optimization"
+  * URLs like github.com/owner/repo/issues/123
+  * "I need help with RabbitMQ, can you suggest some people?"
 - repo_support: Code structure, dependencies, impact analysis, architecture  
 - issue_creation: Creating bugs, features, tracking items
 - documentation_generation: Docs, READMEs, guides, explanations

backend/app/agents/devrel/prompts/response_prompt.py

@@ -26,16 +26,25 @@
 - Avoid complex markdown formatting like **bold** or *italic*
 - Use plain text with clear line breaks
 - Format links as plain URLs: https://example.com
-- Use simple emojis for visual appeal: 🔗 📚 ⚡ 
+- Use simple emojis for visual appeal
 - Keep paragraphs short and scannable
 - Use "→" for arrows instead of markdown arrows
 
+SPECIAL FORMATTING FOR CONTRIBUTOR RECOMMENDATIONS:
+If the task result contains contributor recommendations:
+- Start with "Found X Contributors" 
+- Show search query used and keywords
+- For each contributor: "1. username (Score: X.XXX)"
+- Include their expertise/reason for recommendation
+- End with metadata about search and actionable guidance
+
 Instructions:
 1. Synthesize all information - Use reasoning process, tool results, and task results together
 2. Address the user's needs - Focus on what they're trying to accomplish  
 3. Be actionable - Provide specific steps, resources, or guidance
 4. Stay DevRel-focused - Be encouraging, helpful, and community-oriented
 5. Reference sources - Mention what you researched or considered when relevant
 6. Format for readability - Clean, simple text that displays well
+7. For contributor recommendations - Use the special formatting above to show scores and details
 
 Create a helpful, comprehensive response:"""