docs(template): add concrete-anchor guidance for codegraph_context queries#522
Open
JirA44 wants to merge 1 commit into
Open
docs(template): add concrete-anchor guidance for codegraph_context queries#522JirA44 wants to merge 1 commit into
JirA44 wants to merge 1 commit into
Conversation
…eries Agents writing vague natural-language queries (e.g. 'find async event publishing code') get unrelated results because the FTS index matches on symbol names and annotations, not prose descriptions. A single rule-of-thumb pointing at concrete anchors (class names, method names, framework annotations) closes the gap without extra tooling. Fixes colbymchenry#503
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents querying
codegraph_contextwith vague natural-language descriptions (e.g. "find async event publishing code") get unrelated results because the index matches on symbol names, annotations, and framework keywords — not prose. A concrete example from #503: a query like"Find async execution, message queue, Spring Cloud Stream event publishers"returnedstreamChat/streaminstead of the intended publisher classes.Change: one additional rule-of-thumb in the instructions template written to every agent's config file on install:
No code changes — template-only. Existing installs pick it up on the next
codegraph installrun.Fixes #503