answers.delivery

How-to · 3 min read

How to see what a pull request breaks in other repos

When code is split across several repositories, a small signature change in one can quietly break a caller in another that nobody on the review opened. Reviewers only see the diff in front of them. Tests in the other repository will not run until someone touches it, sometimes days later. You want the pull request itself to tell you who else depends on what you changed.

Published
17 Nov 2026
Delivery
No. 12
Topic
AI and agents
Evidence
10 claims quoted from semlith.com

01
Why it's hard

Code review tools show the diff of one repository, so a caller in a sibling repo is invisible by design. Searching for the function name by hand works until names repeat, or the call goes through a wrapper, or someone forgets to search at all. Asking an AI reviewer to read the diff gives you an opinion that sounds confident but can miss a caller or invent one. And a monorepo migration to make everything visible is a big project for a problem you have today. So most teams find out the slow way, when a build in the other repository goes red after the merge.

This part describes the usual way. It makes no claims about Semlith, so nothing is quoted here.

02
How Semlith does it

Semlith builds an index of your code that maps which piece calls which, across repositories, without any generative model in the lookup. On Semlith Cloud plans, it adds an impact check to GitHub pull requests that posts one status and one comment. That comment lists the symbols that changed, the callers outside the pull request they reach, including ones in other repositories, and anything left with no caller. Each finding points to a file and line, so a reviewer can open it straight away. The index refreshes on each GitHub push, so the check reads current code.

On every pull request, Semlith posts one status check and one comment: what changed, which callers it reachesQuoted from semlith.com
No model reads the diff. Every finding is a graph fact with a file:line.Quoted from semlith.com
There is no generative model in the retrieval path, so the index cannot make anything up.Quoted from semlith.com

03
Step by step

  1. 1Start a Semlith Cloud Pro or Team trial and sign in with GitHub.
  2. 2Add every repository that calls into the code you are changing, so the graph can see across them.
  3. 3Turn on the impact check for your GitHub pull requests.
  4. 4Choose neutral if you want a prompt to look, or failure if any change reaching outside the pull request should fail the check.
  5. 5Open a pull request and read the comment, starting with the callers listed in another repository.
  6. 6Fix or coordinate with the other repo's owners before merging.

04
Tips

Start on neutral. It asks for a look when a caller sits in another repository but never blocks a merge, which lets the team learn what the check reports before you make it strict.

One caller sits in another repository. Neutral asks for a look; it never blocks a merge.Quoted from semlith.com

Read the related documents section too. The comment can point to specs and decision records that name a symbol you touched, which is often where the reason for the old behavior lives.

Related documents · name a touched symbolQuoted from semlith.com

Pay attention to the match labels. A resolved caller means one definition matches, while an inferred one was matched by name only and deserves a second look before you act on it.

matched by name onlyQuoted from semlith.com

Treat the check as facts, not review. It tells you who is reached by a change and leaves judging whether the change is good to the people on the pull request. Pair it with your normal review rather than replacing it, and the two cover different gaps.

Semlith posts facts from the index, never an opinion about the change.Quoted from semlith.com

05
Questions

Is the impact check in the free binary?

No. It is part of Semlith Cloud and listed on the paid plans for GitHub pull requests.

The impact check on GitHub pull requests, neutral or failureQuoted from semlith.com

Can I try it without a card?

Yes. Pro starts with a 14-day trial with no card, and you sign in with GitHub or GitLab.

14 days, no card. Sign in with GitHub or GitLab.Quoted from semlith.com

Can Semlith change code in my repositories?

No. It reads your sources only and never pushes, edits or deletes.

it never pushes, edits or deletes.Quoted from semlith.com

More from Semlith

All 2 answers