typescript-check

Run tsc and ESLint to detect, interpret, and prioritize TypeScript errors.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/hoard --skill typescript-check-dotbeeps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-check
Source: https://github.com/dotBeeps/hoard/tree/main/morsels/skills/typescript-check
Command: npx skills add https://github.com/dotBeeps/hoard --skill typescript-check-dotbeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers run TypeScript type checking and linting, interpret opaque tsc output, and prioritize fixes so type problems are found and resolved before runtime.

Core Features & Use Cases

  • Type checking and linting orchestration: run tsc and eslint, aggregate their output, and surface the most important failures first.
  • Error interpretation and triage: explain common TS error codes, recommend fixes, and provide a remediation order to reduce cascading errors.
  • Configuration and pi-specific guidance: advise on tsconfig paths, skipLibCheck, and symlink issues common in pi extension projects.
  • Use Case: run pre-commit verification or a CI job to identify import, typing, and API mismatch errors and produce actionable fixes for maintainers.

Quick Start

Run a full TypeScript type check using the project's tsconfig.json and then run eslint to list and auto-fix lintable issues.

Frequently Asked Questions about typescript-check

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

FAQPage Schema
How do I run TypeScript type checking and ESLint to catch errors before runtime?

Run TypeScript type checking and linting by executing tsc and eslint to aggregate output, detect compiler and lint errors, and surface the most critical failures before runtime. The process parses tsc and ESLint output to count, group, and suggest actionable code-level fixes.

What is the best way to interpret opaque tsc output and prioritize compiler errors?

Interpreting opaque tsc output involves parsing TypeScript error codes to explain common failures and recommend fixes. Error triage provides a remediation order to resolve the most important type problems first, reducing cascading errors across the project.

Do I need a tsconfig.json and functioning tsc installation to type check a TypeScript project?

Yes, TypeScript type checking requires access to a tsconfig.json file and a functioning tsc installation. A working eslint installation is also necessary to run linting checks and auto-fix lintable issues within the project environment.

Can I use this for pre-commit checks and CI validation in pi extension projects?

Yes, TypeScript type checking and linting orchestration applies to pi extension projects for local debugging, pre-commit verification, and CI validation. It identifies import, typing, and API mismatch errors while providing configuration guidance for tsconfig paths and symlink issues.

Why are TypeScript type checking errors still showing despite setting skipLibCheck in tsconfig?

TypeScript type checking errors may persist due to tsconfig path misconfigurations or symlink issues common in pi extension projects. Error triage advises on tsconfig paths, skipLibCheck settings, and symlink resolutions to properly configure type checking and eliminate residual errors.