> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-h-pull-request-comment-feedback.md).

# Reference H: Pull request comment feedback

Cortex Cloud posts pull request scan results as comments. This gives authors feedback at the point of introduction without Cortex Cloud access.

| Detection type            | Comment content                                                                                                                                                      |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **SCA vulnerabilities**   | The affected package and version, plus vulnerability IDs, fixed version, CVSS, EPSS, and CISA KEV status. Direct and transitive dependencies are reported separately |
| **Secrets**               | The detected credential finding, presented for removal and rotation                                                                                                  |
| **IaC misconfigurations** | The misconfigured resource and matched detection                                                                                                                     |
| **License miscompliance** | The package and license obligation that triggered the detection                                                                                                      |
| **Malicious packages**    | The package name and version, Malware ID with advisory link, and required removal action                                                                             |

The comment records remediation progress across commits. It records fixes and regressions for previously reported vulnerabilities.

> **Note:** Pull request comments require VCS pull request write access. GitHub requires `pull_requests: Write`. Azure DevOps requires pull request thread access.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-h-pull-request-comment-feedback.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.