TypeScript and JavaScript agent workflows with TGlider
Choose a TypeScript or JavaScript task. Confirm the loaded workspace before you query or change code.
Map a feature across a monorepo
Ask
> Map the checkout feature across this workspace. Identify its projects, exports, components, and callers before proposing edits.
Expected evidence
Feature symbols, owning projects, exports, and callers across the loaded workspace.
Tools: load, get_workspace_root, find_code, list_exports, find_callers
Check package import usage
Ask
> Find files that import zod. Inspect their source to distinguish runtime validation, type-only imports, and test usage.
Expected evidence
Import locations and package metadata. Source inspection distinguishes runtime, type-only, and test usage.
Inspect public API surface before changing exports
Ask
> List exports from the ui package. Find their references in the web app before changing a public component name.
Expected evidence
Exported symbols and their references in the selected consumer project.
Tools: list_project_apis, list_exports, semantic_query, analyze_change_impact
Investigate diagnostics without reading build logs
Ask
> Group diagnostics by file. Inspect the failing source ranges and propose a focused fix.
Expected evidence
Diagnostic groups and source spans in the selected project. Build and test execution remains separate.
Tools: get_diagnostics, diagnostic_hotspots, get_file_contents
Find implementations and callers
Ask
> Find implementations of PaymentGateway. Trace callers of the selected implementation before changing retry behavior.
Expected evidence
Implementation symbols and callers, with unresolved relationships identified.
Tools: find_code, find_implementations, find_callers, get_outgoing_calls
Preview a rename
Ask
> Preview a rename from useCustomerStore to useAccountStore. Apply to live documents only when I request it. Save the complete changed files with version checks, then inspect diagnostics.
Expected evidence
A rename plan with affected files. rename_symbol changes live documents. Preview each write_file save and apply with its disk fingerprint and current document version. Then validate the saved workspace.
Tools: find_code, compute_rename_edits, analyze_change_impact, rename_symbol, get_file_contents, write_file, get_diagnostics
Clean unused private code cautiously
Ask
> Find likely-unused private symbols and parameters in the app project. Explain candidates and exclusions before removing code.
Expected evidence
Candidates with symbol context and exclusions. Public exports and dynamic uses require additional checks.
Tools: find_unused_symbols, find_unused_parameters, get_symbol_info
Keep semantic reads aligned with unsaved editor state
Ask
> Open this modified text as a live document. Inspect its structure and diagnostics. Close it after the analysis; keep disk unchanged.
Expected evidence
Structure and diagnostics for the supplied document version. Closing the document returns analysis to disk content.
Tools: open_document, get_structure, get_diagnostics, close_document