C# agent workflows with Glider
Choose a C# task. Confirm the loaded solution before you query or change code.
Understand a feature before changing it
Ask
> Map the checkout flow in this solution. Find its entry points, related symbols, callers, and tests. Summarize the flow before proposing edits.
Expected evidence
Entry points, relevant symbols, and call relationships for the selected feature. Unresolved paths remain explicit.
Tools: load, search_symbols, find_callers, get_outgoing_calls, get_type_info
Check impact before editing shared code
Ask
> Find references, callers, and change impact for UserValidator. Identify affected projects before proposing edits.
Expected evidence
References and callers of the selected symbol, with affected projects and the limits of the impact analysis.
Tools: resolve_symbol, find_references, find_callers, analyze_change_impact
Preview a symbol rename
Ask
> Resolve CustomerService and preview a rename to AccountService. Show the diff. Apply only when I request it, then inspect diagnostics.
Expected evidence
A preview diff and affected files. After an authorized application, diagnostics describe the changed workspace.
Tools: resolve_symbol, rename_symbol, get_diagnostics
Find real implementations of an interface
Ask
> Find implementations of IPaymentGateway. Inspect source references to identify how the checkout flow selects an implementation.
Expected evidence
Implementation symbols and source references. Dependency injection can require additional configuration or runtime evidence.
Tools: resolve_symbol, find_implementations, find_references, get_type_info
Investigate diagnostics
Ask
> Group diagnostics by file. Inspect the largest groups and propose a focused fix.
Expected evidence
Diagnostic groups, source locations, and a proposed fix. Build and test results require separate commands.
Tools: get_diagnostics, diagnostic_hotspots, get_file_contents
Remove unused code or project references
Ask
> Find likely-unused private symbols, parameters, and direct project references. Explain each candidate before removing code.
Expected evidence
Candidates with scope and exclusions. Reflection and external consumers can require further checks before removal.
Tools: find_unused_symbols, find_unused_parameters, find_unused_project_references
Inspect external package source
Ask
> Inspect the external definition of JsonSerializer.Serialize. Find uses of System.Text.Json in this solution.
Expected evidence
The referenced API definition and its uses in the loaded projects.
Request a bounded source view
Ask
> Find symbols and source ranges relevant to this bug. Continue incomplete results before drawing conclusions.
Expected evidence
Selected symbols and source ranges, with continuation information when results are incomplete.
Tools: get_structure, get_symbol_info, get_file_contents, batch