# Graphite Agent — tools that shaped CodeVetter

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

Review quality depends on the shape and timing of the change.

## What we admire

Graphite brought stacked changes and code review into one workflow, then added an agent reviewer. The product is a reminder that a reviewer is only as usable as the change boundary it receives.

## The principle that stayed

Smaller, well-scoped diffs are easier to reason about, reproduce, and attribute. A system should make the boundary of a review obvious before claiming that a finding covers the whole task.

## Where CodeVetter stands

CodeVetter scopes verification to an exact change and records coverage gaps. We studied Graphite’s workflow; CodeVetter does not manage stacked PRs or use Graphite Agent internally.

## Sources

- [Graphite Agent introduction](https://graphite.com/blog/introducing-graphite-agent-and-pricing) — the creator's own source
- [CodeVetter codebase-context research](https://github.com/Codevetter/codevetter/blob/main/docs/knowledge/codebase-context-tools-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)