Menu
Use GliderMCP for C#/.NET navigation, diagnostics, references, call graphs, impact analysis, and safe refactoring.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use GliderTrace for .NET runtime evidence, test runs, failure summaries, exceptions, counters, traces, dumps, and artifact indexing.
Use TGlider for TypeScript and JavaScript semantic navigation, references, diagnostics, dependency topology, impact analysis, and refactoring.
Use Scout for repo-wide code search in any language - ranked fuzzy discovery, exhaustive strict literal, regex, and word search, plus structural patterns, symbol outlines, and semantic queries.
| name | glider-csharp |
| description | Use GliderMCP for C#/.NET navigation, diagnostics, references, call graphs, impact analysis, and safe refactoring. |
Use GliderMCP when working in a C# or .NET repository and the task needs semantic facts rather than plain text search.
Start by checking server_status. If no workspace is loaded, call load with the relevant .sln, .slnx, or .csproj. Prefer find_code as the front door when the user asks to locate behavior by intent. Use search_symbols, resolve_symbol, or get_symbol_at_position before symbol-specific tools, and treat returned symbolKey values as opaque stable identities.
For edits, gather evidence first with tools such as find_references, find_implementations, find_callers, get_outgoing_calls, analyze_change_impact, get_cascade_impact, get_diagnostics, and diagnostic_hotspots. Prefer preview-first refactoring tools where available. After external edits, use sync for changed .cs files and reload for structural project changes.
For non-C# assets, literal strings, config files, and repo-wide text search, prefer Scout's find when Scout is installed. Glider's own search_text already delegates to Scout when a scout binary is on PATH, and reports which backend answered in data.backend - scout covers every file under the solution root in any language, workspace covers only loaded C# documents. Use shell text search only when neither can answer the question.
