> For the complete documentation index, see [llms.txt](https://appsecexplained.gitbook.io/appsecexplained/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appsecexplained.gitbook.io/appsecexplained/code-review/getting-started.md).

# Getting started

{% hint style="info" %}
Coming soon - I'll be putting together a short course on code review :)
{% endhint %}

## Why code review?

Before we dive into why, it's worth mentioning that this section is related to code review with the intent of finding security vulnerabilities and weaknesses within web applications. Not the typical peer review carried out be development teams. If you're interested in code review in general, this is a good place to start <https://about.gitlab.com/topics/version-control/what-is-code-review/>. From now on, we'll be looking at code review to support pentesting and security research activities.

There are many benefits to code review, and it's a skill that takes time to build. The main benefits are:

* Easily spot certain vulnerabilities or weaknesses
  * Hardcoded credentials
  * Weak encryption
  * Insecure libraries or dependencies
* Find hidden or complex vulnerabilities
* Find malicious code (e.g. backdoors)
* Achieve compliance


---

# 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://appsecexplained.gitbook.io/appsecexplained/code-review/getting-started.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.