torbjorn/my-pal-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

enhance: improve tool prompts with better file request grounding and response guidance

Browse Source 
- Update DEBUG_ISSUE_PROMPT to request files when diagnostics are irrelevant/incomplete
- Clarify question field to specify what information is needed from Claude/user
- Update chat tool format_response to ask Claude to continue with user's request
- Update debug tool format_response to encourage implementing fixes when root cause identified
- Fix line length formatting to comply with 120 char limit

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Fahad
2025-06-10 14:59:18 +04:00
parent 7ab0d42dd3
commit 1be339ecc0
3 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
prompts/tool_prompts.py
View File

@@ -137,8 +137,9 @@ DEBUG_ISSUE_PROMPT = """You are an expert debugger and problem solver. Your role
trace issues to their root cause, and provide actionable solutions. trace issues to their root cause, and provide actionable solutions.
IMPORTANT: If you lack critical information to proceed (e.g., missing files, ambiguous error details, IMPORTANT: If you lack critical information to proceed (e.g., missing files, ambiguous error details,
insufficient context), you MUST respond ONLY with this JSON format: insufficient context), OR if the provided diagnostics (log files, crash reports, stack traces) appear irrelevant,
{"status": "requires_clarification", "question": "Your specific question", "files_needed": ["file1.py", "file2.py"]} incomplete, or insufficient for proper analysis, you MUST respond ONLY with this JSON format:
{"status": "requires_clarification", "question": "What specific information you need from Claude or the user to proceed with debugging", "files_needed": ["file1.py", "file2.py"]}
CRITICAL: Your primary objective is to identify the root cause of the specific issue at hand and suggest the CRITICAL: Your primary objective is to identify the root cause of the specific issue at hand and suggest the
minimal fix required to resolve it. Stay focused on the main problem - avoid suggesting extensive refactoring, minimal fix required to resolve it. Stay focused on the main problem - avoid suggesting extensive refactoring,

2
tools/chat.py
View File

@@ -143,4 +143,4 @@ Please provide a thoughtful, comprehensive response:"""
def format_response(self, response: str, request: ChatRequest) -> str: def format_response(self, response: str, request: ChatRequest) -> str:
"""Format the chat response with actionable guidance""" """Format the chat response with actionable guidance"""
return f"{response}\n\n---\n\n**Claude's Turn:** Evaluate this perspective alongside your analysis to form a comprehensive solution." return f"{response}\n\n---\n\n**Claude's Turn:** Evaluate this perspective alongside your analysis to form a comprehensive solution and continue with the user's request and task at hand."

7
tools/debug.py
View File

@@ -186,4 +186,9 @@ Focus on finding the root cause and providing actionable solutions."""
def format_response(self, response: str, request: DebugIssueRequest) -> str: def format_response(self, response: str, request: DebugIssueRequest) -> str:
"""Format the debugging response""" """Format the debugging response"""
return f"Debug Analysis\n{'=' * 50}\n\n{response}\n\n---\n\n**Next Steps:** Evaluate Gemini's recommendations, synthesize the best fix considering potential regressions, test thoroughly, and ensure the solution doesn't introduce new issues." return (
f"Debug Analysis\n{'=' * 50}\n\n{response}\n\n---\n\n"
"**Next Steps:** Evaluate Gemini's recommendations, synthesize the best fix considering potential "
"regressions, and if the root cause has been clearly identified, proceed with implementing the "
"potential fixes."
)