> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/review-workflow.md). # Review workflow Bring Argos visual changes into your review process across the dashboard, pull requests, and status checks. Once your builds run, Argos brings visual changes into your everyday review process — in the dashboard, on your pull requests, and through your status checks. * [Builds list](/docs/learn/review-workflow/builds-list.md) – Browse, filter, and open the builds for a project * [Review a build](/docs/learn/review-workflow/review-a-build.md) – Request reviewers, comment on exactly what changed, and approve or reject together * [Pull request comments](/docs/learn/review-workflow/pull-request-comments.md) – The comment Argos posts on each pull request with the latest build status * [Summary checks](/docs/learn/review-workflow/summary-checks.md) – The commit status checks Argos reports back to your Git provider * [Tags](/docs/learn/review-workflow/tags.md) – Filter screenshots by tag to focus your review * [Review builds with AI agents](/docs/learn/review-workflow/review-builds-with-ai-agents.md) – Let an AI agent triage visual changes from your assistant or CI * [Automations](/docs/learn/review-workflow/automations.md) – Rules that react to build events and notify Slack, Microsoft Teams, or Discord --- # 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://argos-ci.com/docs/learn/review-workflow.md?ask=&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.