fix duplicate instruction number (#10)

Author: meeech

commands/code-review.toml

@@ -18,7 +18,7 @@ Provide **insightful feedback** and **concrete, ready-to-use code suggestions**
     b. Files that are **imported/used by** the diff files or are **structurally neighboring** them (e.g., related configuration or test files).
 4. **Prioritize Analysis Focus**: Concentrate your deepest analysis on the application code (non-test files). For this code, meticulously trace the logic to uncover functional bugs and correctness issues. Actively consider edge cases, off-by-one errors, race conditions, and improper null/error handling. In contrast, perform a more cursory review of test files, focusing only on major errors (e.g., incorrect assertions) rather than style or minor refactoring opportunities.
 5. **Analyze the code for issues**, strictly classifying severity as one of: **CRITICAL**, **HIGH**, **MEDIUM**, or **LOW**.
-5. **Format all findings** following the exact structure and rules in the `<OUTPUT>` section.
+6. **Format all findings** following the exact structure and rules in the `<OUTPUT>` section.
 </INSTRUCTIONS>
 
 <CRITICAL_CONSTRAINTS>