Behavior is a governed contract
ShipCheck does not only remember review preferences or instructions. Behavior Contracts carry the expectation, owner, approval, risk, enforcement, and proof required from the software itself.
Context helps review a change.Judgment protects the system.
Greptile brings broad codebase context, rules, team learning, AI review, and sandboxed runtime verification through TREX to pull requests. ShipCheck is built around a different unit of knowledge: the behavior your software already depends on. Once ShipCheck discovers or protects that behavior, it can persist beyond the current review and be checked explicitly against future changes.
This is a product-model guide, not a measured accuracy comparison. Inspect benchmark results and methodology →
Context for review. Memory for the system.
Both products can reason beyond a raw diff. ShipCheck centers its product model on treating important software behavior as a governed, versioned contract, complete with explicit invariants, criticality, enforcement, evidence requirements, lifecycle outcomes, historical origin, and a risk-aware ship decision. It does not rely only on reviewer context, learned preferences, or reusable review rules.
ShipCheck
Every guard has future outcomes
Protected behavior can be evaluated as preserved, intentionally changed, violated, restored, or newly introduced as the repository evolves.
The expectation has provenance
ShipCheck can connect protected behavior to supporting implementation, tests, related files, and the historical commit where that behavior became true.
Evidence governs the verdict
A bounded verification agent and deterministic evidence policy validate citations, coverage, contradictions, and required proof before contract risk affects the ship verdict.
Greptile
Runtime verification with TREX
Greptile documents targeted test execution in a sandbox and runtime evidence attached to PR findings. This guide does not establish a measured advantage for ShipCheck.
Codebase graph context
Greptile builds repository graphs and uses broader code relationships during pull-request review.
Rules and team learning
Greptile supports custom review rules, directory-scoped configuration, and learned team preferences.
Cross-repository context
Related repositories can be supplied as review context for changes that cross repository boundaries.
What changes in practice.
These differences determine whether context disappears after review or becomes durable protection for the next change.
A rule says what reviewers should check. A Behavior Guard says what the software must continue doing.
That distinction matters for regressions. ShipCheck can preserve an authorization guarantee, validation behavior, API contract, state transition, safeguard, error behavior, or other invariant as repository memory rather than simply feeding another instruction into future reviews.
ShipCheck records what happened to the behavior.
A future PR is not only another review. ShipCheck can attach an explicit outcome to a known expectation: preserved, changed intentionally, violated, restored, or introduced.
The reason an invariant exists stays connected to it.
Historical Origin can trace the implementation and test history behind a Behavior Guard so a future developer can understand not only what must remain true, but where that expectation came from.
Compare the operating model.
A direct view of the features that shape how each product reasons about change.
| Capability | ShipCheck | Greptile | Context |
|---|---|---|---|
| Repository-aware AI review | Yes | Yes | Both use repository context beyond the changed lines. |
| Cross-file reasoning | Yes | Yes | |
| Cross-repository context | Yes: mapped provider and consumer Behavior Contracts | Yes | |
| Persistent review preferences / rules | Repository controls and protected behaviors | Yes: custom rules and learned preferences | |
| Persistent software behavior as a first-class object | Yes: Behavior Contracts V2 | Not its primary abstraction | |
| Explicit behavior lifecycle | Preserved, changed, violated, restored, introduced | Not assessed here; consult current vendor documentation | |
| Historical origin of protected behavior | Yes | Not assessed here; consult current vendor documentation | |
| Deterministic verification alongside AI | Yes | Static checks and sandboxed runtime verification through TREX | |
| Coding-agent independence | Yes | Yes |
Context helps the reviewer understand today’s PR. Memory protects tomorrow’s.
ShipCheck turns important repository behavior into durable expectations that future code has to keep satisfying.