# Ellipsis — tools that shaped CodeVetter

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

The useful review loop continues from finding to attempted fix.

## What we admire

Ellipsis connects review feedback with an agent that can make a change and run checks. That closes an important gap between a comment that identifies a problem and an actual repair that a developer can inspect.

## The principle that stayed

A generated fix needs its own verification. The fact that an agent acted on a comment does not establish that the behavior is repaired or that the patch stayed within scope.

## Where CodeVetter stands

CodeVetter’s agent-fix packets and review-proof states make the proposed repair reviewable and distinguish fixed, reproduced, and unchecked outcomes. Ellipsis was a workflow reference, not an integration.

## Sources

- [Ellipsis code review documentation](https://www.ellipsis.dev/docs/code-review) — 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)