Warning: blindly using code-review-graph can make model faster but noticeably worse at code understanding

[cxc1357]

The current injected instructions push the agent to always use code-review-graph first.

In practice, this improves speed and reduces token usage, but it also makes the model over-trust graph summaries and miss important implementation details in source code. The result is shallower reasoning, more template-like edits, and weaker understanding of edge cases, recovery logic, compatibility code, and tests.

It may be helpful to append guardrails like this to the injected instructions:

Guardrails

• Use graph tools first to narrow scope, not to replace source reading.
• Do not make code changes based only on graph summaries.
• For any non-trivial change, read the actual implementation files and relevant tests before concluding.
• When changing behavior, database logic, migrations, retries, fallbacks, recovery, or compatibility code, always verify the exact source.
• If graph and source disagree, trust the source code.
• In final answers, explain which files/functions/tests were actually read.

[starrye]

I also encountered the same problem. May I ask where this "Guardrails" should be written?

[cxc1357]

After installation, there should be prompt files such as GEMINI.md CLAUDE.md ... Put the guardrails at the end of the file that matches the IDE you're using

[SuperPerro95]

This is hands down the best tip i've got during my first week of Claude Code trying to save tokens. CAVEMAN is slow, and doesn't work with Graphify or code-review-graph. Now i'm only using C-R-G with these guardrails and is fast, and accurate. Fixes things first try.

[starrye]

This is hands down the best tip i've got during my first week of Claude Code trying to save tokens. CAVEMAN is slow, and doesn't work with Graphify or code-review-graph. Now i'm only using C-R-G with these guardrails and is fast, and accurate. Fixes things first try.

I also used CAVEMAN. So, could you please explain what C-R-G is?

[SamRil1995]

This is hands down the best tip i've got during my first week of Claude Code trying to save tokens. CAVEMAN is slow, and doesn't work with Graphify or code-review-graph. Now i'm only using C-R-G with these guardrails and is fast, and accurate. Fixes things first try.

I also used CAVEMAN. So, could you please explain what C-R-G is?

C- Code, R- Review, G- graph

[starrye]

This is hands down the best tip i've got during my first week of Claude Code trying to save tokens. CAVEMAN is slow, and doesn't work with Graphify or code-review-graph. Now i'm only using C-R-G with these guardrails and is fast, and accurate. Fixes things first try.

I also used CAVEMAN. So, could you please explain what C-R-G is?

C- Code, R- Review, G- graph

ok～，Abandon the use of CAVEMAN。But in the afternoon, I asked Claude Code and he replied that it was not affected. Both could be used simultaneously.

[SuperPerro95]

r

yes, I know. But honestly, i feels slower. I feels like its blocking some tool uses.

Plus, I don't like it to technical