gdctxlisted

# gdctx Skill Use this skill by default when a task needs command output, search results, git diff/status, test logs, lint/build output, or large file reads that may produce more context than the agent should load directly. The user does not need to explicitly ask for gdctx usage. **Search rule (hard):** any text, symbol, or pattern search over project code goes through `keryx ctx rg "<pattern>"`, never a bare `rg`/`grep`. This holds even for a single "targeted" search and even when you skip gdgraph/gdwiki — `ctx rg` compresses the output while raw `rg` dumps it into context. Raw `rg`/`grep` is allowed only as a last resort when `keryx ctx rg` is unavailable or demonstrably cannot express the query, and the reason must be stated in the routing audit. ## Workflow 1. Check whether `.metaproject/modules/gdctx.md` exists. 2. For potentially long output, prefer `keryx ctx ...` over raw shell output by default. 3. For project navigation or file relationship questions, use gdgraph first when available, then use gdctx for compact command/file output. 4. Treat gdctx summaries as navigation context. Verify important claims against source files before editing or reporting. 5. Use raw output only when the compact summary is insufficient. ## Commands ```bash keryx ctx status keryx ctx diff keryx ctx rg "<pattern>" keryx ctx read <file> --mode outline keryx ctx read <file> --mode compact keryx ctx run -- <command...> keryx ctx show latest ``` ## Enforcement (optional) The search ru