Files
wehub-resource-sync a06f331eb8
CI / benchmark (push) Has been skipped
install-script / posix-syntax (push) Successful in 6m1s
CI / build-onnx (push) Failing after 6m43s
init-smoke / dry-run (push) Failing after 15m57s
security / govulncheck (push) Has been cancelled
security / trivy-fs (push) Has been cancelled
CI / test (1.26, ubuntu-latest) (push) Has been cancelled
Scorecard supply-chain security / Scorecard analysis (push) Has been cancelled
CI / test (1.26, macos-latest) (push) Has been cancelled
CI / build-windows (push) Has been cancelled
CI / lint (push) Has been cancelled
install-script / powershell-syntax (push) Has been cancelled
install-script / install (macos-14) (push) Has been cancelled
install-script / install (ubuntu-latest) (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:33:42 +08:00

99 lines
2.9 KiB
Plaintext

=== home/.gemini/antigravity/knowledge/gortex-workflow/artifacts/gortex-instructions.md ===
---
type: "Knowledge Item"
description: "Gortex Workflow and Tools for Antigravity"
---
# Gortex Engine Usage
This codebase is indexed by Gortex, an in-memory knowledge graph code intelligence engine.
**MANDATORY:** You MUST prioritize using the Gortex CLI via `run_command` instead of using standard text searches (`grep_search`) or full file reads (`view_file`). This drastically improves token efficiency and prevents hallucination.
## Setup
If the daemon is not tracking your target repos, register the current repo so the graph tools activate:
```bash
gortex track .
```
## Standard Workflow Translation
| Instead of... | You MUST use... (via `run_command`) |
|---|---|
| `grep_search` to find a class or function | `./gortex query symbol <name> --format text` (AST-aware search) |
| `grep_search` to find all references | `./gortex query usages <id>` (zero false positives) |
| `view_file` to read a whole file to find a method | `./gortex query symbol <name>` or `./gortex query callers <func_id>` |
| Guessing what breaks during a refactor | `./gortex query dependents <id>` (impact analysis) |
| Creating circular dependencies | Evaluate `./gortex query deps <id>` first |
## Example Usage
### 1. View Architecture and Communities
```bash
./gortex query stats
```
### 2. Find specific symbol definition
```bash
./gortex query symbol MyController
```
### 3. Trace blast radius
If you are modifying `core/parser.go::Parse`, check what will break:
```bash
./gortex query dependents core/parser.go::Parse --depth 2
```
This gives you perfectly accurate AST-level analysis, guaranteeing safe edits.
=== home/.gemini/antigravity/knowledge/gortex-workflow/metadata.json ===
{
"summary": "MANDATORY: Instructions on how to use the local gortex engine CLI to significantly improve codebase intelligence. Antigravity must use run_command with gortex query over standard file read commands.",
"references": ["artifacts/gortex-instructions.md"]
}
=== home/.gemini/antigravity/mcp_config.json ===
{
"mcpServers": {
"gortex": {
"args": [
"mcp"
],
"command": "gortex",
"env": {
"GORTEX_INDEX_WORKERS": "8"
}
}
}
}
=== home/.gemini/settings.json ===
{
"hooks": {
"AfterTool": [
{
"hooks": [
{
"command": "gortex hook --agent antigravity",
"description": "Gortex graph context + stale-index hint",
"name": "gortex",
"timeout": 10000,
"type": "command"
}
],
"matcher": "run_shell_command|search_file_content|glob"
}
],
"SessionStart": [
{
"hooks": [
{
"command": "gortex hook --agent antigravity",
"description": "Gortex session orientation",
"name": "gortex",
"timeout": 10000,
"type": "command"
}
]
}
]
}
}