DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to fail CI when a committed diagram drifts from the code with Qgraphflow

Validate committed diagrams against the repo in CI so stale architecture views get flagged.

Short answer: Commit your generated diagrams under docs/qgraphflow/ so each has a graph.json; then add a workflow file that runs on push and pull_request, using actions/checkout, actions/setup-node with node-version 22, and the validation loop from the README; run npx -y qgraphflow validate "$graph" --input-only --repo-root . for each graph.json, as the README's CI example does. All steps.

Who it is forA team lead or DevOps engineer who keeps diagrams in the repo and wants them checked on every push and pull request.

The problemDiagrams in docs go stale silently after refactors, so they describe code that no longer exists.

The outcomeA CI job that fails when a recorded file is gone, a line range no longer fits, or a recorded symbol has moved, and names the lines where the symbol now sits.

What you need first

  • Node.js 22 or later
  • A plugin-capable client such as Claude Code, Codex, Cursor or Qoder, with model access configured
  • A local checkout of the application project you want to diagram

Steps

  1. Commit your generated diagrams under docs/qgraphflow/ so each has a graph.json.
  2. Add a workflow file that runs on push and pull_request, using actions/checkout, actions/setup-node with node-version 22, and the validation loop from the README.
  3. Run npx -y qgraphflow validate "$graph" --input-only --repo-root . for each graph.json, as the README's CI example does.
  4. When the job fails, open a session and enter /q-flow CI says docs/qgraphflow/<diagram-folder> is out of date. Refresh it. (inferred, check the README)
  5. Commit the refreshed diagram and confirm the job passes.

Prompt for your agent

In the repo <repo-path>, add a GitHub Actions workflow that validates every docs/qgraphflow/*/graph.json with `npx -y qgraphflow validate` using --input-only and --repo-root, as shown in the QGraphFlow README. Run the validation locally and report any diagram whose recorded files, lines or symbols no longer match the source.

Caveat. Validation checks recorded files, line ranges and symbols against the repo, so it does not detect relationships that were never recorded in the diagram.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for supermax92/qgraphflow and "Fail CI when a committed diagram drifts from the code"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer