/gograph

name: gograph
version: "0.1.0"
description: "Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Adds AST-aware call graphs, blast-radius analysis, impact and security-flow candidates, and 61 query, analysis, and workflow capabilities through the local gograph MCP server."
argument-hint: "gograph stats | gograph plan UserService.Login | gograph review --uncommitted"
allowed-tools: Bash, Read
homepage: https://gograph.identuum.ai
repository: https://github.com/ozgurcd/gograph
author: ozgurcd
license: MIT
user-invocable: true

gograph: Go Repository Intelligence

`gograph` is a local, AST-aware Go code intelligence engine that exposes 61 query, analysis, and workflow capabilities over the Model Context Protocol (65 endpoints including session lifecycle). It gives terminal LLMs (Claude Code, Cursor agents, OpenClaw) a structural view backed by a persisted or in-memory graph. `gograph_context` combines evidence that may otherwise require several navigation and source calls; actual savings depend on the task.

`gopls` provides live compiler-backed navigation, diagnostics, implementations, refactoring, and experimental MCP support. `gograph` complements it with a persisted repository graph, composed change-analysis workflows, and policy gates for coding agents.

When to invoke this skill

Activate whenever the user is working in a Go repository:

• Reading code, asking what a function does, or tracing a behavior across files.
• Planning, editing, refactoring, or deleting any Go symbol (function, method, struct, interface, package).
• Reviewing a Go diff or unstaged changes.
• Hunting a bug, auditing for security issues, or measuring complexity / coupling.

If a `.go` file is in the CWD or the user mentions a Go symbol, type, package, or interface by name, the skill applies.

Do NOT invoke for non-Go work. The skill is Go-scoped.

Prerequisite

The gograph binary must be installed and on `$PATH`:

go install github.com/ozgurcd/gograph/cmd/gograph@latest

Verify with `gograph --version`. The marketplace plugin supplies this workflow guidance; it does not install the binary or register an MCP server. Register `gograph mcp <project-path>` for each project using the client's MCP setup. Packaged and generated registrations keep refresh persistence off by default.

Mandatory workflow (enforced)

1. **At the start of any Go coding session**, invoke `gograph_capabilities` to confirm what the connected server exposes. 2. **Confirm graph health** before symbol queries. MCP creates an in-memory AST graph when the artifact is missing, unreadable, unsafe, or has an unsupported source-policy marker, and refreshes source analysis per call. Invoke `gograph_stats` with no parameters and require `build_status=complete`; a build with zero successful parses never replaces the previous graph, while partial failures are reported explicitly. When durable precise enrichment is needed, run CLI `gograph build . --precise`; if compilation prevents it, use CLI `gograph build .` and explain the fallback. 3. **For structural symbol / type / function discovery, use `gograph_query` instead of `grep`, `rg`, `find`, or glob.** Text search also matches comments and string literals; `gograph_query` returns AST-derived matches. Continue to use text search for literal strings, documentation, ordinary non-sensitive configuration, and non-Go files. 4. **Before editing any Go symbol**, invoke `gograph_plan` with `symbol=<symbol>`. The plan returns callers, tests connected to the symbol, and a blast-radius estimate. Edit decisions should reference the plan. 5. **To understand a function or method**, invoke `gograph_context` with `symbol=<symbol>`. This single call combines node + source + callers + callees + statically mapped tests; inspect source or `gopls` when the evidence is incomplete. 6. **After editing Go code**, invoke `gograph_review` with `uncommitted=true`; MCP refreshes source analysis before the review. If the task requires a durable precise artifact for later CLI or server processes, run CLI `gograph build . --precise` first. Run the repository's required tests and checks separately.

High-value tools

| Tool | Use case | |---|---| | `gograph_capabilities` | Discover what the connected server exposes | | `gograph_query` with `term=<term>` or `terms=[...]` | AST-derived structural symbol search | | `gograph_context` with `symbol=<symbol>` | Node + source + callers + callees + tests in one call | | `gograph_plan` with `symbol=<symbol>` | Pre-edit blast radius + callers + tests | | `gograph_review` with `uncommitted=true` | Post-edit coverage check | | `gograph_impact` with `symbol=<symbol>` | What breaks if this changes | | `gograph_callers` / `gograph_callees` with `function=<symbol>` | Explicit call-graph traversal | | `gograph_implementers` with `interface=<interface>` | All types implementing an interface | | `gograph_routes` | HTTP route discovery across handler / service / repository layers | | `gograph_sql` | SQL query inventory across the codebase | | `gograph_complexity` | Cyclomatic complexity per function | | `gograph_godobj` | God-object detection | | `gograph_coupling` | Package coupling / instability scores | | `gograph_diagram` | Mermaid architecture diagrams | | `gograph_errors` with optional `term=<term>` | Error inventory | | `gograph_errorflow` with `query=<term>` | Error propagation paths | | `gograph_flow` | Potential HTTP/JSON/env paths to SQL, process, filesystem, and outbound HTTP sinks | | `gograph_changes` | Diff source against the trusted persisted graph, or MCP startup fallback when no usable artifact exists | | `gograph_tests` with optional `symbol=<symbol>` | Tests connected to a symbol | | `gograph_check` | Policy checks, including changed-route tests, coverage, orphans, API drift, arity, and complexity |

The live surface is 65 MCP endpoints