Skip to content

Catch the pull request that undoes last month’s fix.

ShipCheck is behavioral memory for software. It learns what your code must keep doing from the bugs you’ve already fixed, then checks every pull request against it.

Runs as a check on your GitHub pull requests, next to your CI and your AI reviewer.

Example pull request
Merged March 4fix: reject expired sessions#318

214 commits later

Opened today by a coding agentRefactor session middleware#412
All checks passed
  • Build
  • Lint and types
  • Unit tests

The test that covered this was deleted in the same pull request.

Breaks a protected behaviorShipCheck

Expired sessions must always be rejected.

Learned from #318, March 4
api/sessions.ts
assertSessionIsActive(session);assertSessionExists(session);
Replayed “rejects an expired session”base passeshead fails

An expired session would be accepted as valid.

More of your code is now written by people and agents who weren’t there for the last outage.

A diff shows which lines changed. It can’t tell you that one of them was the fix for a bug your customers hit in March. Your repository already knows. ShipCheck makes sure it remembers.

Three steps. Then it runs on every pull request.

  1. It learns from your history

    ShipCheck reads your code, tests and git history. Every bug you fixed left a clue about what must stay true, and ShipCheck turns those clues into candidate behaviors.

  2. You choose what to keep

    Approve the behaviors that matter. Each one becomes a Behavior Guard, written in plain language and linked to the code and commit it came from.

  3. Every pull request is checked

    On each pull request, every guard is checked and reported as preserved, changed, violated or new, with the evidence that decided it.

A behavior has a history. Now you can see it.

Git remembers how your code changed. ShipCheck remembers what it’s supposed to keep doing.

Every Behavior Guard keeps its own record: where it came from, every pull request that kept it intact, every intentional change, and every time something broke it.

Explore Behavior Guards
Only project owners can update a project.
  1. IntroducedFix #207, January 19

    Learned from the commit that closed the bug.

  2. Preserved128 pull requests

    Checked on every change, without anyone asking.

  3. Changed on purposePull request #331

    Admins may now update projects too. Approved by the owner, so the guard was updated.

  4. ViolatedPull request #455

    Any signed-in user could edit. Caught before merge.

  5. RestoredPull request #456

    The owner check came back. The guard is green again.

Keep your AI reviewer. Add a memory.

Reviewers are good at reading a diff. ShipCheck carries what your team learned into every diff after it.

AspectAn AI reviewer asks“Does this code look right?”ShipCheck asks“Did this break something we already promised?”
Looks atThis pull requestThis pull request and every behavior you protected
Learns fromReview comments and preferencesPast bug fixes, tests and team decisions
Tells youWhat looks wrong in the diffWhich promise broke, where it came from, and the proof

Quiet unless it can show you why.

A check your team learns to ignore is worse than no check. ShipCheck only blocks with evidence.

  • Evidence on every finding

    Each verdict links to the code, the guard and, where it can, the same scenario replayed on both revisions.

  • No proof means no verdict

    When the evidence isn’t there, ShipCheck says “inconclusive” rather than guessing that a change is safe.

  • Read-only until you act

    Scans read your repository. Fixes and tests are only written when you choose to apply them.

  • You make the call

    Approve a change as intentional and the guard updates with it. Your team keeps the final say on every merge.

How is this different from an AI code reviewer?

An AI reviewer reads the pull request in front of it. ShipCheck keeps a lasting record of what your software must keep doing, learned from your code and past fixes, and checks every pull request against that record. Most teams run both.

Do I need to write every behavior down?

No. ShipCheck finds important behavior in your existing code and mines past bug fixes for candidates. You approve the ones worth protecting.

Does every result come with runtime proof?

Not always. Available evidence depends on your repository and tests. ShipCheck labels which results are backed by replayed tests and which by code analysis, and marks a result inconclusive when it can’t prove it.

Will ShipCheck change my code?

Only when you ask. Scans are read-only. Applying a suggested fix or regression test always takes an explicit action from you.

What does it work with?

GitHub pull requests today. ShipCheck installs as a GitHub App on the repositories you choose and reports as a check on each pull request.

Your next pull request is a good place to start.

Connect a repository, approve the behaviors worth keeping, and let ShipCheck remember them from here on.