> For the complete documentation index, see [llms.txt](https://docs.coveragelabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coveragelabs.io/services/security-review/context-and-cleanup.md).

# Context & Cleanup

## Diagrams & User flows

We create detailed diagrams and user flows to visualize the architecture and functionality of your codebase. This approach helps identify potential design flaws and improves the overall understanding of the engineering team involved in the engagement.

{% hint style="info" %}
**Note:** These diagrams are provided to the client as a deliverable and can be used freely for marketing and development purposes.
{% endhint %}

## Static Analysis

We utilize various static analysis tools, including [Slither](https://github.com/crytic/slither), [Slitherin](https://github.com/pessimistic-io/slitherin), and [Aderyn](https://github.com/Cyfrin/aderyn), to identify vulnerabilities and known anti-patterns early. This automated review ensures the code is free from unnecessary clutter and establishes a solid foundation for the engagement.

## Gas Optimizations

We analyze the codebase to identify opportunities for gas optimizations, concentrating on enhancing cost-efficiency during deployment and runtime while maintaining readability.


---

# 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://docs.coveragelabs.io/services/security-review/context-and-cleanup.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.