Skip to content

docs(agents): note graphify update cadence is periodic, not per-edit #497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mforce merged 4 commits into from
Aug 10, 2026
Merged

docs(agents): note graphify update cadence is periodic, not per-edit #497

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3f27cc4
docs(agents): relocate AGENTS.md rationale to docs/decisions, compres…
claude Aug 4, 2026
0dea657
docs(agents): note graphify update cadence is periodic, not per-edit
claude Aug 10, 2026
428c598
merge main into claude/github-issue-413-2t0jgw
claude Aug 10, 2026
4054530
docs(agents): explain why graphify update isn't run per-commit
claude Aug 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,4 +267,4 @@ Rules:
- Dirty graphify-out/ files are expected after hooks or incremental updates; dirty graph files are not a reason to skip graphify. Only skip graphify if the task is about stale or incorrect graph output, or the user explicitly says not to use it.
- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).
- Users need to periodically run `graphify update .` to keep the graph current (AST-only, no API cost) — exact frequency is unknown yet. Don't run it as part of every code change: bundling it into each commit inflates PRs with unrelated changed lines and works against keeping PRs small.
Loading