> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers/code-review-facilitator.md).

# Code Review Facilitator

Elevate your code reviews with the power of real-time coverage insights. Utilize the User Story Coverage Report to identify areas lacking sufficient testing, proactively guiding reviewers towards potential blind spots. 

***

## Step-by-Step Tutorial

<details>

<summary><strong>1. Access the User Story's / Subtask's Coverage</strong></summary>

* The code reviewer should open the user story or subtask in Jira and navigate to the "Coverage" tab.\
  ![](https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/9lbLxiNQah5aIukhMkd9/image.png)\
  \
  **Note:** If the tab is missing, the user story deployment isn't complete. Refer to the[Deployment Guide](/knowledgebase/guides/user-story-coverage/technical-overview/deployment-guide.md) for further details.

</details>

<details>

<summary><strong>2. Deep Dive into Method List</strong></summary>

* Open the detailed coverage report to scrutinize individual methods.\
  \
  ![](https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/XPZIvgi72jL9GDfC1mBf/image.png)
* The report is on the User Story level. Find the relevant subtask in the report and open the method list.\
  \
  ![](https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/aTDgraoB2PV3cVpVXxUb/image.png)

</details>

<details>

<summary>3. Scan the Method List</summary>

* Quickly identify coverage gaps by looking for methods marked red (no tests) or orange (only unit tests).\
  \ <img src="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/U0oeRyQJAxzb5mDYHA2D/image.png" alt="" data-size="original">
* Prioritize methods currently under review.

</details>

<details>

<summary>4. <strong>Assess Coverage</strong></summary>

* Use your organization's standards and testing strategy to judge if coverage is sufficient.
* **Important:** Some organizations run additional tests after code review. Only assess coverage for test types already executed.

</details>

<details>

<summary>5. <strong>Address Critical Gaps</strong></summary>

* If critical methods lack coverage, leave comments on the pull request or discuss directly with the developer.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers/code-review-facilitator.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.