Skip to content

docs(agent): optimize agent prompt template and fix non-existent wiki reference #2124

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

Open
rfirmn wants to merge 1 commit into
base: v8
Choose a base branch
from
+10 −7
Open

docs(agent): optimize agent prompt template and fix non-existent wiki reference #2124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
17 changes: 10 additions & 7 deletions graphify/always_on/agents-md.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,15 @@
## graphify

This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
This project has a knowledge graph at `graphify-out/` with project structure, symbol relationships, community analysis, and cross-file dependencies.

When the user types `/graphify`, use the installed graphify skill or instructions before doing anything else.
When the user types `/graphify`, use the installed Graphify skill or instructions before doing anything else.

Rules:
- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
- 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).
- For codebase questions, first run `graphify query "<question>"` when `graphify-out/graph.json` exists. Only fall back to source search if Graphify cannot answer or the requested information is outside the indexed graph.
- Prefer Graphify over full-project searches whenever possible. Use source code browsing only to inspect implementation details after Graphify has identified the relevant files or symbols.
- Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than `GRAPH_REPORT.md` or raw grep output.
- 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.
- Read `graphify-out/GRAPH_REPORT.md` for broad architecture review or when `graphify query`, `graphify path`, or `graphify explain` do not surface enough context.
- Use `graphify-out/graph.html` only when an interactive visualization is explicitly needed; do not rely on it for automated reasoning.
- If `graphify-out/graph.json` does not exist, assume the knowledge graph has not been generated yet. Inspect the source normally or ask the user to run `graphify update .`.
- After modifying code that changes project structure, symbols, modules, or relationships, run `graphify update .` to keep the graph current (AST-only, no API cost). Minor changes such as comments, formatting, or documentation generally do not require updating the graph.