DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check which services call which, and catch broken links with Vibex

Record each cross-service call once and fail when a client, handler, or endpoint moves.

Who it is forA platform engineer working across several repositories who needs a System view of service-to-service calls.

The problemNobody knows which service calls which, and renamed or removed endpoints break calls silently.

The outcomeA System view diagram and a check that lists broken calls and endpoints that nothing calls.

What you need first

  • Node.js and npx, for the npx commands in the README
  • A Prisma schema, OpenAPI document, or GraphQL SDL file in the project, or source code the tool can read
  • Claude Code or Codex if you want to use vibeX as an agent skill

Steps

  1. vibex links system.links.json docs --repo bff=../bff --repo orders=../orders --check

Prompt for your agent

Using the repos at <repo paths>, write system.links.json describing the calls between services, then run vibeX links with --check. Report any broken client, handler, or endpoint, and list endpoints nothing calls. Verify the check fails when a handler is renamed in a test copy.

Caveat. The check reads the code it is pointed at, so repositories not passed with --repo cannot be verified.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page