Loading...
Loading...
Search TypeScript SYMBOLS (functions, types, classes) - NOT text. Use Glob to find files, Grep for text search, LSP for symbol search. Provides type-aware results that understand imports, exports, and relationships.
npx skill4agent add plaited/development-skills typescript-lsp*.ts*.tsx*.js*.jsx| Tool | Purpose |
|---|---|
| Glob | Find files by pattern |
| Grep | Search text content |
| lsp-find | Search TypeScript symbols |
| lsp-hover | Get type info + TSDoc documentation |
| lsp-refs | Find all references to a symbol |
| lsp-analyze | Batch analysis of file structure |
| Task | Use LSP | Use Grep/Glob |
|---|---|---|
| Find all usages of a function/type | ✅ | ❌ Misses re-exports, aliases |
| Search for a symbol by name | ✅ | ❌ Matches strings, comments |
| Get type signature + TSDoc | ✅ | ❌ Not possible |
| Understand file exports | ✅ | ❌ Doesn't resolve re-exports |
| Find files by pattern | ❌ | ✅ |
| Search non-TS files (md, json) | ❌ | ✅ |
| Search for text in comments/strings | ❌ | ✅ |
lsp-findlsp-symbolslsp-analyze --exportslsp-referenceslsp-hoverlsp-findlsp-hover/Users/name/project/src/file.ts./src/file.ts../other/file.tsmy-package/src/module.tsBun.resolve()bunx @plaited/development-skills lsp-hover <file> <line> <char>filelinecharbunx @plaited/development-skills lsp-hover src/utils/parser.ts 42 10bunx @plaited/development-skills lsp-symbols <file>bunx @plaited/development-skills lsp-symbols src/utils/parser.tsbunx @plaited/development-skills lsp-refs <file> <line> <char>bunx @plaited/development-skills lsp-refs src/utils/parser.ts 42 10bunx @plaited/development-skills lsp-find <query> [context-file]querycontext-filebunx @plaited/development-skills lsp-find parseConfig
bunx @plaited/development-skills lsp-find validateInput src/lib/validator.tsbunx @plaited/development-skills lsp-analyze <file> [options]--symbols, -s--exports, -e--hover <line:char>--refs <line:char>--all# Get file overview
bunx @plaited/development-skills lsp-analyze src/utils/parser.ts --all
# Check multiple positions
bunx @plaited/development-skills lsp-analyze src/utils/parser.ts --hover 50:10 --hover 75:5
# Before refactoring: find all references
bunx @plaited/development-skills lsp-analyze src/utils/parser.ts --refs 42:10# 1. Get exports overview
bunx @plaited/development-skills lsp-analyze path/to/file.ts --exports
# 2. For specific type info, hover on interesting symbols
bunx @plaited/development-skills lsp-hover path/to/file.ts <line> <char># 1. Find all references first
bunx @plaited/development-skills lsp-refs path/to/file.ts <line> <char>
# 2. Check what depends on it
# Review the output to understand impact# Search for similar implementations
bunx @plaited/development-skills lsp-find handleRequest
bunx @plaited/development-skills lsp-find parseConfig# Before writing code that uses an API, verify its signature
bunx @plaited/development-skills lsp-hover path/to/api.ts <line> <char>{
"contents": {
"kind": "markdown",
"value": "```typescript\nconst parseConfig: (options: Options) => Config\n```"
},
"range": { "start": {...}, "end": {...} }
}[
{
"name": "symbolName",
"kind": 13,
"range": { "start": {...}, "end": {...} }
}
]{
"file": "path/to/file.ts",
"exports": [
{ "name": "exportName", "kind": "Constant", "line": 139 }
]
}lsp-analyze