ReddRadar
Topic: database-management
10 skills in this topic.
-
gitnexus-debugging
Trace bugs through call chains using knowledge graph
debba/tabularis 1,064
-
gitnexus-exploring
Navigate unfamiliar code using GitNexus knowledge graph
debba/tabularis 1,064
-
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
debba/tabularis 1,064
-
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
debba/tabularis 1,064
-
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
debba/tabularis 1,064
-
gitnexus-guide
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?"
debba/tabularis 1,064
-
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
debba/tabularis 1,064
-
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
debba/tabularis 1,064
-
gitnexus-impact-analysis
Analyze blast radius before making code changes
debba/tabularis 1,064
-
gitnexus-refactoring
Plan safe refactors using blast radius and dependency mapping
debba/tabularis 1,064