Fix markdown formatting in review commands for consistency

Author: Johan Broberg

.claude/commands/review-pr.md

@@ -67,7 +67,7 @@ Write the consolidated review to a markdown file using the Write tool:
 
 Use this exact format:
 
-```markdown
+````markdown
 # Code Review Report
 
 ---
@@ -79,7 +79,6 @@ PR Number:           #$ARGUMENTS
 PR Title:            [title from gh pr view]
 PR Iteration:        1
 Review Date/Time:    [ISO 8601 timestamp]
-Reviewer:            code-review-manager
 Subagents Used:      architecture-reviewer, code-reviewer, test-coverage-reviewer
 ```
 
@@ -133,13 +132,13 @@ Subagents Used:      architecture-reviewer, code-reviewer, test-coverage-reviewe
 ## Approval Status
 
 **Final Status:** [APPROVED / APPROVED WITH MINOR NOTES / CHANGES REQUESTED / REJECTED]
-```
+````
 
 ### Structured Issue Format
 
 For EVERY finding, use this structure:
 
-```markdown
+````markdown
 #### [CRM-001] Issue Title
 
 | Field | Value |
@@ -166,7 +165,7 @@ IMPORTANT: Include the relevant diff snippet from the PR that shows the code bei
 
 **Suggestion:**
 [Specific recommendation]
-```
+````
 
 ### Step 5: Report to User
 

.claude/commands/review-staged.md

@@ -68,7 +68,7 @@ Write the consolidated review to a markdown file using the Write tool:
 
 Use this exact format:
 
-```markdown
+````markdown
 # Code Review Report (Staged Changes)
 
 ---
@@ -78,7 +78,6 @@ Use this exact format:
 ```
 Review Type:         Pre-commit (Staged Changes)
 Review Date/Time:    [ISO 8601 timestamp]
-Reviewer:            code-review-manager
 Subagents Used:      architecture-reviewer, code-reviewer, test-coverage-reviewer
 ```
 
@@ -134,13 +133,13 @@ Subagents Used:      architecture-reviewer, code-reviewer, test-coverage-reviewe
 **Status:** [READY TO COMMIT / FIX ISSUES FIRST / NEEDS DISCUSSION]
 
 [Brief explanation of the status]
-```
+````
 
 ### Structured Issue Format
 
 For EVERY finding, use this structure:
 
-```markdown
+````markdown
 #### [CRM-001] Issue Title
 
 | Field | Value |
@@ -166,7 +165,7 @@ IMPORTANT: Include the relevant diff snippet that shows the code being discussed
 
 **Suggestion:**
 [Specific recommendation]
-```
+````
 
 ### Step 5: Report to User