# Review Anatomy (https://tenki.cloud/docs/reviewer/review-anatomy)

> For the complete documentation index, see [llms.txt](https://tenki.cloud/llms.txt)

This page explains exactly how a Tenki review appears in your PR and how to interpret each component.



Summary [#summary]

The **Summary** is a high-level, decision-oriented overview of the PR.

It appears immediately and updates as the analysis progresses.

![TenkiCodeReviewerReviewAnatomy](https://tenki.cloud/images/reviewer/review-anatomy.png)

Structure: [#structure]

* What has been reviewed
* Findings grouped by severity
* Short recap of key issues
* Collapsed list of files reviewed
* Security risk assessment: An explicit security assessment of the PR. Only high-confidence, PR-fixable security issues are reported.
  * **LOW**, No security vulnerabilities identified
  * **MEDIUM**, Security edge cases introduced
  * **HIGH**, Exploitable vulnerabilities found

Review Comment [#review-comment]

The **Review Comment** contains the full breakdown of findings.

It appears at the same time as the Summary and updates live during analysis.

![TenkiCodeReviewerReviewComment2](https://tenki.cloud/images/reviewer/review-comment.png)

![TenkiCodeReviewerReviewComment2](https://tenki.cloud/images/reviewer/review-comment-2.png)

Structure: [#structure-1]

**Security**

* High / Medium / Low severity
* Includes explanations when applicable

**Code Quality**

* General code health assessment
* Structural or maintainability concerns

**Other Observations**

Additional relevant signals, such as:

* Performance risks
* Architectural concerns
* Notable patterns introduced
* Repeated anti-patterns

**Recommendation**

A single, clear outcome:

* **APPROVE**, Safe to merge
* **APPROVE with minor suggestions**, Non-blocking issues
* **CHANGES REQUESTED**, Blocking issues must be addressed

Reporting Scope [#reporting-scope]

Tenki only reports issues that:

* Are introduced by this PR
* Could cause bugs, security risks, or instability
* Can be addressed within the PR