# Qodo / PR-Agent — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/qodo

A review should be close to tests and the intent behind a change.

## What we admire

Qodo’s review work and open PR-Agent made the review pipeline inspectable to a wide audience. The emphasis on tests, descriptions, and repository instructions is especially relevant when an agent has written the patch.

## The principle that stayed

Pull request comments, test generation, and task context are separate evidence sources. Treating each as a distinct input makes it easier to see what a reviewer actually knows.

## Where CodeVetter stands

CodeVetter uses task intent, command results, and reproducible artifacts in one verification bundle. We studied Qodo’s workflow; we do not use PR-Agent as CodeVetter’s review engine.

## Sources

- [PR-Agent documentation](https://docs.pr-agent.ai/) — the creator's own source
- [CodeVetter competitive landscape](https://github.com/Codevetter/codevetter/blob/main/docs/knowledge/competitive-landscape.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)