fix: markdown formatting in code review examples

[timdeschryver]

Updated markdown code blocks for example comments in the code review instructions.

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new instruction, prompt, agent, or skill file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, or skill with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.

---

Description

The markdown code blocks are currently not well formatted in the "Example Comments" section. This also impacts the "Review Checklist" section.

This PR uses 4 ticks to create the example markdown templates, so that the code blocks (and text) of the markdown content blocks are correctly formatted.

Before:

After:

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New collection file.
• New skill file.
• Update to existing instruction, prompt, agent, collection or skill.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull request overview

This PR fixes markdown formatting in the code review instructions file by correctly nesting code blocks within example comments. The issue was that triple backticks were used for both outer and inner code blocks, preventing proper rendering of the nested code examples.

Changes:

• Updated example comment blocks to use quadruple backticks (````) instead of triple backticks (```) to properly nest code blocks