1294caa7fa
Complete rebuild of 22-year-old PHP CMS as modern SaaS: Database (15 migrations, 42+ tables): - Foundation: account_settings, audit_log, GDPR register, cms_files - Module Engine: modules, fields, records, permissions, relations + RPC - Members: 45+ field member profiles, departments, roles, honors, SEPA mandates - Courses: courses, sessions, categories, instructors, locations, attendance - Bookings: rooms, guests, bookings with availability - Events: events, registrations, holiday passes - Finance: SEPA batches/items (pain.008/001 XML), invoices - Newsletter: campaigns, templates, recipients, subscriptions - Site Builder: site_pages (Puck JSON), site_settings, cms_posts - Portal Auth: member_portal_invitations, user linking Feature Packages (9): - @kit/module-builder — dynamic low-code CRUD engine - @kit/member-management — 31 API methods, 21 actions, 8 components - @kit/course-management, @kit/booking-management, @kit/event-management - @kit/finance — SEPA XML generator + IBAN validator - @kit/newsletter — campaigns + dispatch - @kit/document-generator — PDF/Excel/Word - @kit/site-builder — Puck visual editor, 15 blocks, public rendering Pages (60+): - Dashboard with real stats from all APIs - Full CRUD for all 8 domains with react-hook-form + Zod - Recharts statistics - German i18n throughout - Member portal with auth + invitation system - Public club websites via Puck at /club/[slug] Infrastructure: - Dockerfile (multi-stage, standalone output) - docker-compose.yml (Supabase self-hosted + Next.js) - Kong API gateway config - .env.production.example
65 lines
3.4 KiB
Markdown
65 lines
3.4 KiB
Markdown
---
|
|
name: gitnexus-guide
|
|
description: "Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\""
|
|
---
|
|
|
|
# GitNexus Guide
|
|
|
|
Quick reference for all GitNexus MCP tools, resources, and the knowledge graph schema.
|
|
|
|
## Always Start Here
|
|
|
|
For any task involving code understanding, debugging, impact analysis, or refactoring:
|
|
|
|
1. **Read `gitnexus://repo/{name}/context`** — codebase overview + check index freshness
|
|
2. **Match your task to a skill below** and **read that skill file**
|
|
3. **Follow the skill's workflow and checklist**
|
|
|
|
> If step 1 warns the index is stale, run `npx gitnexus analyze` in the terminal first.
|
|
|
|
## Skills
|
|
|
|
| Task | Skill to read |
|
|
| -------------------------------------------- | ------------------- |
|
|
| Understand architecture / "How does X work?" | `gitnexus-exploring` |
|
|
| Blast radius / "What breaks if I change X?" | `gitnexus-impact-analysis` |
|
|
| Trace bugs / "Why is X failing?" | `gitnexus-debugging` |
|
|
| Rename / extract / split / refactor | `gitnexus-refactoring` |
|
|
| Tools, resources, schema reference | `gitnexus-guide` (this file) |
|
|
| Index, status, clean, wiki CLI commands | `gitnexus-cli` |
|
|
|
|
## Tools Reference
|
|
|
|
| Tool | What it gives you |
|
|
| ---------------- | ------------------------------------------------------------------------ |
|
|
| `query` | Process-grouped code intelligence — execution flows related to a concept |
|
|
| `context` | 360-degree symbol view — categorized refs, processes it participates in |
|
|
| `impact` | Symbol blast radius — what breaks at depth 1/2/3 with confidence |
|
|
| `detect_changes` | Git-diff impact — what do your current changes affect |
|
|
| `rename` | Multi-file coordinated rename with confidence-tagged edits |
|
|
| `cypher` | Raw graph queries (read `gitnexus://repo/{name}/schema` first) |
|
|
| `list_repos` | Discover indexed repos |
|
|
|
|
## Resources Reference
|
|
|
|
Lightweight reads (~100-500 tokens) for navigation:
|
|
|
|
| Resource | Content |
|
|
| ---------------------------------------------- | ----------------------------------------- |
|
|
| `gitnexus://repo/{name}/context` | Stats, staleness check |
|
|
| `gitnexus://repo/{name}/clusters` | All functional areas with cohesion scores |
|
|
| `gitnexus://repo/{name}/cluster/{clusterName}` | Area members |
|
|
| `gitnexus://repo/{name}/processes` | All execution flows |
|
|
| `gitnexus://repo/{name}/process/{processName}` | Step-by-step trace |
|
|
| `gitnexus://repo/{name}/schema` | Graph schema for Cypher |
|
|
|
|
## Graph Schema
|
|
|
|
**Nodes:** File, Function, Class, Interface, Method, Community, Process
|
|
**Edges (via CodeRelation.type):** CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, MEMBER_OF, STEP_IN_PROCESS
|
|
|
|
```cypher
|
|
MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"})
|
|
RETURN caller.name, caller.filePath
|
|
```
|