From repo-cortex
Routes codebase and domain questions to the right tool: **GitNexus MCP** for code architecture, **graphify CLI** for documents and domain knowledge.
How this skill is triggered — by the user, by Claude, or both
Slash command
/repo-cortex:cortexThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Routes codebase and domain questions to the right tool: **GitNexus MCP** for code architecture, **graphify CLI** for documents and domain knowledge.
Routes codebase and domain questions to the right tool: GitNexus MCP for code architecture, graphify CLI for documents and domain knowledge.
| Tool | Use case |
|---|---|
mcp__gitnexus__context | Semantic code search |
mcp__gitnexus__impact | Impact of changing a symbol |
mcp__gitnexus__route_map | Call path between two points |
mcp__gitnexus__tool_map | All functions/exports in a module |
mcp__gitnexus__shape_check | Type/schema consistency |
mcp__gitnexus__detect_changes | Diff impact since last commit |
mcp__gitnexus__rename | Safe rename with impact preview |
mcp__gitnexus__api_impact | API contract change analysis |
mcp__gitnexus__query | Graph traversal query |
| Command | Use case |
|---|---|
graphify query "<question>" | BFS traversal |
graphify query "<question>" --dfs | DFS traversal |
graphify explain "<node>" | Node + neighbors |
graphify path "A" "B" | Shortest concept path |
graphify-out/GRAPH_REPORT.md → domain "what"mcp__gitnexus__context → structural "how"/cortex init [path]gitnexus analyze "${1:-.}" & graphify update "${1:-.}" & wait
/cortex status[ -f graphify-out/graph.json ] && echo "graphify: OK" || echo "graphify: not built"
gitnexus list
/cortex query <question>Route by question type. Ambiguous → run both, merge.
/cortex impact <symbol>mcp__gitnexus__impact(symbol="<symbol>")
/cortex explain <concept>mcp__gitnexus__context(query="<concept>")graphify explain "<concept>"/cortex add <url>graphify add "<url>"
/cortex rebuild [--force]gitnexus analyze . && graphify update .
| Question | Primary | Secondary |
|---|---|---|
What calls functionX? | GitNexus route_map | — |
Impact of changing moduleY? | GitNexus impact | — |
| What does concept Z mean? | graphify explain | GitNexus context |
All usages of apiW? | GitNexus tool_map | — |
| Architecture overview? | graphify GRAPH_REPORT.md | GitNexus context |
Safe to rename X? | GitNexus rename + shape_check | — |
| Summarize paper / doc? | graphify query | — |
| Feature flow end-to-end? | GitNexus route_map | graphify query |
graphify update . # after code changes — AST-only, no API cost
gitnexus analyze . # re-parse changed files
graphify add <url> # add new external knowledge
npx claudepluginhub felimet/claude-repo-cortex --plugin repo-cortexProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.