repo-cortex

repo-cortex

Claude Code plugin unifying GitNexus (code architecture) and graphify (documents/knowledge) into a single /cortex interface.

繁體中文說明 →

What it does

• Routes code-structure questions to GitNexus MCP (AST-precise, 13 tools)
• Routes document/domain questions to graphify CLI
• Proactively suggests /cortex when graph traversal beats recursive grep/find
• Injects graph context before every Grep/Glob/Bash search op

Prerequisites

# GitNexus
npm install -g gitnexus
claude mcp add gitnexus -- npx -y gitnexus@latest mcp

# graphify
uv tool install graphifyy
graphify claude install

Install

From GitHub (once published)

Add to ~/.claude/settings.json:

{
  "extraKnownMarketplaces": {
    "repo-cortex": {
      "source": {
        "source": "github",
        "repo": "felimet/claude-repo-cortex"
      }
    }
  }
}

Then: claude plugin install repo-cortex

Local install (development)

claude plugin install /path/to/claude-repo-cortex

CLAUDE.md configuration

After installing the plugin, add the following to your ~/.claude/CLAUDE.md (global) or .claude/CLAUDE.md (project-level):

# cortex
- **cortex** (repo-cortex plugin) - unified knowledge graph: routes code-architecture
  questions to GitNexus MCP tools, document/domain questions to graphify CLI. Trigger: `/cortex`
When the user types `/cortex`, invoke the Skill tool with `skill: "cortex"` before doing anything else.

## cortex proactive suggestions (always active)

Detect the following situations and proactively offer a one-line `/cortex` suggestion BEFORE
proceeding with the less efficient alternative.
Format: `[cortex] <situation> → <suggested command>`.
Do NOT suggest if `/cortex init` output files are absent AND repo is not in `gitnexus list`.

| Situation | Suggest |
|-----------|---------|
| "how does X work", "explain architecture", "what does this codebase do" | `/cortex query "X"` or read `graphify-out/GRAPH_REPORT.md` |
| "what calls X", "who uses Y", "where is Z referenced" | `/cortex impact X` |
| "what breaks if I change X", "impact of modifying Y" | `/cortex impact X` |
| "safe to rename X" | GitNexus `rename` + `shape_check` via `/cortex` |
| About to run multiple Glob/Grep to understand code structure | `/cortex query "<question>"` |
| User pastes a paper/doc URL | `/cortex add <url>` |
| Session starts in repo with no `graphify-out/` and not in gitnexus index | `/cortex init` (one-time) |
| End-to-end flow question spanning multiple modules | `/cortex query` + GitNexus `route_map` |
| Debugging a bug across multiple files | `/cortex impact <entry_symbol>` first |

Suggestion rules:
- One line only. No multi-paragraph explanation.
- Offer suggestion, then wait. Do not auto-execute `/cortex` commands.
- If user declines or ignores, proceed — do not repeat for same question.
- If both graphs absent and repo small (<10 files), skip.

Skills

Skill	Trigger	Purpose
cortex	/cortex	Unified entry point + routing
cortex-init	/cortex-init	Build both graphs for current repo
cortex-impact	/cortex-impact <symbol>	Impact analysis via GitNexus
cortex-query	/cortex-query <question>	Smart-routed graph query

Hooks

Hook	Trigger	Purpose
SessionStart	Every session	Inject proactive suggestion rules
PreToolUse	Grep/Glob/Bash	Inject graph context when available
PostToolUse	Bash	Suggest /cortex for recursive grep/find/cat patterns

Quick start

cd your-project
/cortex-init                                    # build both graphs (one-time)
/cortex-query "how does the auth flow work"
/cortex-impact authMiddleware
/cortex add https://paper-url                   # add external knowledge

License

MIT

Acknowledgements

This plugin is built on top of two excellent open-source projects:

• GitNexus by @abhigyanpatwari — AST-precise code intelligence and MCP server for Claude Code
• graphify by @safishamsi — Knowledge graph builder for documents, papers, and domain knowledge