Repository navigation
Cross-link the cross-repo and agent-usage cookbooks - #153
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![graphify-labs-staging[bot]](https://avatars.githubusercontent.com/in/4517131?s=60&v=4){kind=small}
There was a problem hiding this comment.
Graphify reviewed this change.
No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.
Not checked: tests were not run; no formal proof of the changed code.
Graphify review — findings
Cross-links the two cookbooks so each next-steps section now surfaces the other as the immediate follow-on card. Readers who finish “make agents use the graph” are offered the cross-repo recipe, and readers who finish the cross-repo recipe are offered the agent rules, with the layout tightened to two columns to keep the cards visible. The verification paragraph in cross-repo-dependencies also gains a direct sentence pointing back to the agent cookbook.
No blocking issues surfaced.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 31 functions depend on the 31 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 31 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 31 function(s) in the blast radius were not formally verified this run
Links the two new cookbooks to each other: inline mentions now link to the other cookbook, and each adds the other to Next steps (CardGroup now 2 columns for 4 cards).
mint broken-linkspasses.