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.
BetaShipCheck vs. Greptile
Context helps review code.Memory protects behavior.
Greptile brings broad codebase context, rules, team learning, and AI review 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.
Comparison based on publicly documented product capabilities as of September 2026. Features may change.
The difference
Both products can reason beyond a raw diff. ShipCheck stands apart by treating important software behavior as a governed, versioned contract — with explicit invariants, criticality, enforcement, evidence requirements, lifecycle outcomes, historical origin, and a risk-aware ship decision — instead of relying only on reviewer context, learned preferences, or reusable review rules.
Why ShipCheck
Review the change.Remember the behavior.
ShipCheck is not trying to win by producing more comments. Its advantage is retaining important behavioral knowledge after the pull request is over and bringing it back when the next change arrives.
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
What it is built around.
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.
The ShipCheck advantage
The repository should remember why behavior matters.
A reviewer can understand the current code. ShipCheck goes further by retaining the important expectations that understanding reveals and checking them again later.
01
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.
02
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.
03
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.
Behavior Contract v3
Persistent repository expectation
Expected behavior
Only the subscription owner may cancel a subscription.
Origin retained with governed runtime + test evidence
Behavior lifecycle
01
Introduced
Guard established
02
Preserved
Behavior intact
03
Preserved
Behavior intact
04
Violated
Regression found
05
Restored
Behavior fixed
Side by side
What each product actually stores and verifies.
This comparison avoids treating every kind of “memory,” rule, history, or context as equivalent. ShipCheck's strongest distinction is explicit behavioral state carried across repository history.
Capability
ShipCheck
Behavioral memory
Greptile
Current documented product
Repository-aware AI review
Both use repository context beyond the changed lines.
Cross-file reasoning
Cross-repository context
Not currently a core capability
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
No equivalent first-class behavior lifecycle documented
Historical origin of protected behavior
No equivalent first-class origin workflow documented
Deterministic verification alongside AI
Primarily AI-driven review
Coding-agent independence
The ShipCheck thesis
A repository should not need to rediscover the same critical behavior every time someone opens another pull request.
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.
Start with GitHub