Fix: agent sample

Author: cristipufu

samples/github-helper-agent/main.py

@@ -92,7 +92,10 @@ async def make_graph():
         async with ClientSession(read, write) as session:
             tools = await load_mcp_tools(session)
 
-            model = ChatAnthropic(model="claude-3-5-sonnet-latest")
+            model = ChatAnthropic(
+                model="claude-3-7-sonnet-20250219",
+                temperature=0.2,
+            )
 
             # Create the conversation history
             async def hydrate_history(input: PullRequestInfo) -> GraphState:
@@ -195,40 +198,36 @@ def pr_prompt(state: GraphState) -> GraphState:
                 in_reply_to = state.get("in_reply_to")
                 if in_reply_to:
                     label = f"{AI_GENERATED_LABEL} [{in_reply_to}]_\n"
-                    command_message = f"The CURRENT command is '{state['command']}' from review comment id #{in_reply_to}. EXECUTE the CURRENT command and provide detailed feedback."
+                    command_message = f"The CURRENT command is '{state['command']}'. EXECUTE the CURRENT command in_reply_to #{in_reply_to} and provide detailed feedback."
                 else:
                     label = f"{AI_GENERATED_LABEL}_\n"
                     command_message = f"The CURRENT command is '{state['command']}. EXECUTE the CURRENT command and provide detailed feedback."
 
                 """Create a prompt that incorporates PR data."""
-                system_message = f"""You are a professional developer with experience in code reviews and GitHub pull requests.
-                You are working with repo: {state["owner"]}/{state["repo"]}, PR #{state["pull_number"]}.
-
-                IMPORTANT INSTRUCTIONS:
-                1. ALWAYS get the contents of the changed files in the current PR
-                2. ALWAYS use the contents of the changed files as context when replying to a user command.
-                3. ALWAYS start your responses with "{label}" to properly tag your comments.
-                4. When you reply to a comment, make sure to address the specific request.
-                5. When reviewing code, be thorough but constructive - point out both issues and good practices.
-                6. You MUST use the available tools to post your response as a PR comment or perform the PR code review.
-
-                COMMANDS YOU SHOULD UNDERSTAND:
-                - "review": Perform a full code review of the PR
-                - "summarize": Summarize the changes in the PR
-                - "explain <file>": Explain what changes were made to a specific file
-                - "suggest": Suggest improvements to the code
-                - "test": Suggest appropriate tests for the changes
-
-                WORKFLOW:
-                1. Gather the contents of the changed files for the current PR
-                2. Analyze the available PR data and understand what the user is asking for
-                3. Use the appropriate tools to gather any additional information needed
-                4. Prepare your response based on the request
-                5. [IMPORTANT] Based on the user's command:
-                    - if the command has a review comment id, REPLY TO THE REVIEW COMMENT WITH THE SPECIFIED ID using tool add_pull_request_review_comment
-                    - else POST PULL REQUEST REVIEW using tool create_pull_request_review
-
-                Remember: The user wants specific, actionable feedback and help with their code.
+                system_message = f"""You are a professional developer and GitHub reviewer.
+
+                You are reviewing Pull Request #{state["pull_number"]} in repo {state["owner"]}/{state["repo"]}.
+
+                YOU MUST FOLLOW THESE RULES WITHOUT EXCEPTION:
+
+                1. ALWAYS get the contents of the changed files BEFORE writing any response.
+                2. ALWAYS use the contents of the changed files as context.
+                3. ALWAYS start ALL responses with exactly: "{label}" (no exceptions).
+                4. ALWAYS POST your responses to GitHub via available tools:
+                - If `in_reply_to` is provided, REPLY to the existing review comment ID {in_reply_to} using `add_pull_request_review_comment`.
+                - If no `in_reply_to` or previous tool call failed, POST a new review using `create_pull_request_review`.
+
+                COMMANDS you can receive:
+                - "review": Do a complete code review, pointing out issues and good practices.
+                - "summarize": Summarize the PR changes.
+                - "explain <file>": Explain changes made to a specific file.
+                - "suggest": Suggest improvements.
+                - "test": Suggest tests for the changes.
+
+                IMPORTANT:
+                - Do not make assumptions.
+                - Do not skip steps.
+                - If you cannot complete the command for any reason, you MUST reply with an error comment on GitHub.
 
                 {command_message}
                 """

samples/github-helper-agent/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "github-helper-agent"
-version = "0.0.8"
+version = "0.0.10"
 description = "An automated agent that reviews GitHub pull requests and provides feedback"
 authors = [{ name = "Cristi Pufu", email = "[email protected]" }]
 dependencies = [