6 skills · sorted by relevance
Code understanding tool selection. Use when exploring architecture, finding definitions, tracing call chains, assessing blast radius of changes, or debugging code paths in the Genesis codebase.
The English summary is being prepared. Showing the original description.
Use when navigating or refactoring code with a language server - choosing between semantic (LSP), exact-text (rg), and fuzzy/semantic search; anchoring LSP calls by position; gating degraded results; and disclosing tool substitutions, in any language.
The English summary is being prepared. Showing the original description.
Compiler-level code intelligence via native LSP — definitions, references, types, call hierarchies, and diagnostics.
The English summary is being prepared. Showing the original description.
Route codebase-structure questions (who calls X, where used, change-impact) to an existing code-graph first: impact, tests-for, dead cheaper, never more precise; grep routine. Also 'call graph'.
The English summary is being prepared. Showing the original description.
Use for AST/dep graph/complexity analysis of Python code.
The English summary is being prepared. Showing the original description.
Index a codebase with GitNexus and serve an interactive knowledge graph via web UI + Cloudflare tunnel.
The English summary is being prepared. Showing the original description.