shysssthanhtri/gitnexus-guide
skills/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?"
tools
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add shysssthanhtri/AI-tools 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
shysssthanhtri/work-on-ticket-plan
testing
VerifiedTrustedCommunity
Execute an existing Jira ticket implementation plan phase by phase. Use when asked to "work on ticket CM-1234", "implement the plan for CM-1234", "start working on the plan", or "execute the next phase". Reads the plan from docs/<ticket-id>/plan.md, captures a pre-implementation full test baseline in plan/progress docs, presents each phase for user approval before coding, updates progress after each phase, and operates inside the dedicated git worktree. After the last phase is committed, runs the full test suite, fixes regressions (skipping known pre-existing failures), then presents a full change summary for user review and creates a GitHub draft PR using the create-draft-pr skill.
SKILL.mdUpdated Apr 25, 2026
shysssthanhtri/typescript-mcp-server-generator
tools
VerifiedTrustedCommunity
Generate a complete MCP server project in TypeScript with tools, resources, and proper configuration
SKILL.mdUpdated Apr 25, 2026
shysssthanhtri/setup-new-work
tools
VerifiedTrustedCommunity
Use when starting work on a Jira ticket. Fetches ticket details via Atlassian MCP (for branch naming and a local story snapshot), creates an isolated git worktree with branch feature/<ticket-id>-<slug>-<platform>, and writes docs/<ticket-id>/<ticket-id>.md in the worktree.
SKILL.mdUpdated Apr 25, 2026
shysssthanhtri/plan-jira-ticket
documentation
VerifiedTrustedCommunity
Create a work plan for a Jira ticket. Use when asked to plan work, create a plan for a ticket, break down a Jira issue, or prepare implementation steps for a Jira ticket ID like CM-1234. Reads local ticket details, deeply analyzes requirements and root causes, proposes up to three optimized solutions (not workarounds) with pros and cons, asks the user to choose, then finalizes the plan with that choice under docs/<ticket-id>/.
SKILL.mdUpdated Apr 25, 2026