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

How to document a service and fail CI when the docs drift with Vibex

Write checkable docs whose claims are anchored to code and re-verified on every build.

Who it is forA tech lead who wants service documentation that stays accurate without someone rewriting it by hand.

The problemProse docs go stale silently, so readers cannot tell which statements still match the code.

The outcomeA docs spec with claims that show a confidence state, and a CI step that exits with an error when a claim no longer holds.

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 docs system.docs.json specs/ --repo . --check
  2. vibex dashboard docs/index.html docs --title "Payments platform" --repo .

Prompt for your agent

In the repo <repo path>, write a claims-based document for the <service name> service in system.docs.json, run vibeX docs with --check, and report how many claims are verified. Verify that the check exits with code 1 when you change an anchored line in a test copy.

Caveat. vibeX catches drift after the claims are written, so a misreading in the first draft stays verified until a person reviews it.

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