Skill Detail

Expose repository code intelligence to agents with Gortex

Use Gortex to index one or more repositories into a local code graph and expose symbol, call-chain, blast-radius, review, and refactoring tools through MCP, CLI, API, or web UI.

Developer ToolsMCP
Developer Tools MCP Published
⭐ 840 GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill expose-repository-code-intelligence-to-agents-with-gortex Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Gortex binary, local git repositories, optional MCP-capable coding agent or CLI/API client
Install & setup
Install the Gortex release binary, run gortex init in the target repository, start the daemon or MCP server, and connect the detected coding assistant or MCP client to the generated configuration.
Author
Gortex contributors
Publisher
Open Source
Last updated
Jul 11, 2026
Quick brief

Use Gortex when a coding agent needs structured repository understanding without reading large files or dumping entire codebases into context. The workflow is to install the single binary, run gortex init in the repository, let it build a local graph across one or more repos, and expose focused code-intelligence tools through its MCP server, CLI, API, or web UI. Invoke it instead of raw grep, manual file pasting, or ad hoc repository summaries when the agent needs symbol lookup, call chains, blast-radius analysis, semantic search, code actions, PR review, or cross-repo contract tracing. The scope boundary is the local repository graph and agent-facing query surface; it is not a generic IDE, search engine, or language-server listing.

How it works

What this skill actually does

Inputs and prerequisites: Gortex binary, local git repositories, optional MCP-capable coding agent or CLI/API client.

Setup notes: Install the Gortex release binary, run gortex init in the target repository, start the daemon or MCP server, and connect the detected coding assistant or MCP client to the generated configuration.

Source and verification boundary: use https://gortex.dev/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.