kryptobaseddev/gitnexus-guide
.claude/skills/gitnexus/gitnexus-guide/SKILL.md
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?"
$ install --global
skillsauthnpx skillsauth add kryptobaseddev/cleo gitnexus-guideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 26, 2026, 4:23 PM41.0s1 file scanned
SKILL.md
- 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:
- Read
gitnexus://repo/{name}/context— codebase overview + check index freshness - Match your task to a skill below and read that skill file
- Follow the skill's workflow and checklist
If step 1 warns the index is stale, run
npx gitnexus analyzein 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
MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"})
RETURN caller.name, caller.filePath
Related Skills
kryptobaseddev/signaldock-connect
tools
VerifiedTrustedCommunity
Connect any AI agent to SignalDock for agent-to-agent messaging. Use when an agent needs to: (1) register on api.signaldock.io, (2) install the signaldock runtime CLI, (3) send/receive messages to other agents, (4) set up SSE real-time streaming, (5) poll for messages, (6) check inbox, or (7) connect to the SignalDock platform. Triggers on: "connect to signaldock", "register agent", "send message to agent", "agent messaging", "signaldock setup", "install signaldock", "agent-to-agent".
149SKILL.mdUpdated Apr 15, 2026
kryptobaseddev/ct-validator
development
VerifiedTrustedCommunity
Compliance validation for verifying systems, documents, or code against requirements, schemas, or standards. Performs schema validation, code compliance checks, document validation, and protocol compliance verification with detailed pass/fail reporting. Use when validating compliance, checking schemas, verifying code standards, or auditing protocol implementations. Triggers on validation tasks, compliance checks, or quality verification needs.
149SKILL.mdUpdated Apr 15, 2026
kryptobaseddev/ct-task-executor
testing
VerifiedTrustedCommunity
General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.
149SKILL.mdUpdated Apr 15, 2026
kryptobaseddev/ct-stickynote
tools
VerifiedTrustedCommunity
Quick ephemeral sticky notes for project-wide capture before formal classification
149SKILL.mdUpdated Apr 15, 2026