This feature request is to implement the following user case.

Use‑case:
Reviewers often leave ambiguous comments that prompt additional questions for the author of the code changes.

The CM can configure Repository Settings to provide a comment template that sets clear expectations.

Example of a comment template to establish expectations:

• [Observation]: Describe exactly what is happening in the current code.
• [Recommendation]: I suggest/recommend changing Statement A to Statement B.
  • Statement A (Current): [Paste original code]
  • Statement B (Proposed): [Paste improved code]

• [Rationale]: Explain the "Why." Outline the specific concerns with Statement A, potential bugs or maintenance issues it could cause in the future, and how Statement B mitigates those concerns.