code-inspection

Find symbol usages, import relationships, definitions, and type errors in TypeScript or Vue codebases.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/yearofthedan/weaver --skill code-inspection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-inspection
Source: https://github.com/yearofthedan/weaver/tree/main/.claude/skills/code-inspection
Command: npx skills add https://github.com/yearofthedan/weaver --skill code-inspection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need reliable, compiler‑aware insight to find where symbols are used, which files import a module, and what type errors exist, without fragile text searches or manual tsc runs.

Core Features & Use Cases

  • Find all files that import a given file, handling path aliases, barrel re‑exports, extensionless imports, and Vue SFCs.
  • Retrieve every reference to a symbol across the project, including through re‑exports and barrels.
  • Jump to the actual definition of a symbol, following re‑exports.
  • Check type errors in a single file or across the whole project (capped at 100 files).

Quick Start

Ask the assistant to list all references to the symbol at src/a.ts line 10 column 5.

Frequently Asked Questions about code-inspection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find all references to a symbol across a TypeScript project?

To find all references to a symbol across a TypeScript project, query the project graph to retrieve every usage, including those routed through barrel re-exports and Vue SFCs. This compiler-aware approach avoids fragile text searches.

How do I check type errors across my Vue and TypeScript codebase?

Check type errors across your Vue and TypeScript codebase by querying the project graph for validation results. This method caps at 100 files and bypasses manual tsc execution, providing precise compiler-aware error reporting.

Does this approach handle path aliases and barrel re-exports when finding symbol definitions?

Yes, locating symbol definitions handles path aliases and barrel re-exports. It jumps directly to the actual definition by following re-exports, ensuring accurate navigation across extensionless imports and Vue SFCs.

What is the best way to find files that import a specific TypeScript module?

The best way to find files that import a specific TypeScript module is to query the project graph for import relationships. This returns all dependent files while resolving path aliases and barrel re-exports automatically.

Why locate symbol usages using a project graph instead of grep?

Locating symbol usages via a project graph provides compiler-aware insight, unlike fragile grep text searches. It accurately resolves path aliases, extensionless imports, and Vue SFCs to validate and navigate code precisely.