diff --git a/kaizen/helpers/output.py b/kaizen/helpers/output.py
index 2da7b114..46802c14 100644
--- a/kaizen/helpers/output.py
+++ b/kaizen/helpers/output.py
@@ -13,13 +13,7 @@
 
 PR_COLLAPSIBLE_TEMPLATE = """
 <details>
-<summary>{comment}</summary>
-
-##### Reason
-{reasoning}
-
-##### Confidence
-{confidence}
+<summary>[{confidence}] -> {reasoning}</summary>
 </details>
 """
 
diff --git a/kaizen/llms/prompts.py b/kaizen/llms/prompts.py
index 415344ac..38b2a413 100644
--- a/kaizen/llms/prompts.py
+++ b/kaizen/llms/prompts.py
@@ -8,7 +8,7 @@
 
 CODE_REVIEW_PROMPT = """
 You are an experienced software engineer tasked with reviewing a pull request.
-Your goal is to provide a comprehensive code review that evaluates the code changes, identifies potential issues or areas for improvement,
+Your goal is to provide a comprehensive code review that evaluates the code changes, identifies potential issues,
 and provides constructive feedback to the developer.
 
 Using the provided information, generate a detailed code review with feedback organized as a JSON object. Only include sections with relevant feedback, omitting sections without feedback. Follow this structure:
@@ -36,8 +36,6 @@
 Potential section topics:
 - "Code Quality"
 - "Performance" 
-- "Testing"
-- "Documentation"
 - "Potential Issues"
 - "Improvements"
 
@@ -83,8 +81,6 @@
 Potential section topics:
 - "Code Quality"
 - "Performance" 
-- "Testing"
-- "Documentation"
 - "Potential Issues"
 - "Improvements"
 
@@ -107,7 +103,6 @@
 
 1. Summarize the main purpose and scope of the changes.
 2. Highlight any significant modifications, refactoring, or new features introduced.
-3. Explain the motivation or rationale behind the changes.
 
 Provide output in following format:
 {{"desc": "<PR_DESCRIPTION_IN_MARKDOWN>"}}