scan-typescript

Detect TypeScript violations like any usage and ts-ignore via rg scans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/TrevorPLam/agency --skill scan-typescript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-typescript
Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/scan-typescript
Command: npx skills add https://github.com/TrevorPLam/agency --skill scan-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers identify and surface TypeScript violations such as any usage, ts-ignore, and non-strict patterns, enabling teams to improve type safety and code quality across a codebase.

Core Features & Use Cases

  • Automated detection of problematic TS patterns including any, ts-ignore, and non-strict constructs.
  • Excludes test files and non-TypeScript files to reduce noise and focus on real issues.
  • Outputs findings in a structured format and appends unique issues to tasks/issues.md with content hashes for deduplication, while tracking progress for post-run review.
  • Reproducible scans with timeout safeguards and deterministic results to fit into CI pipelines.

Quick Start

Run a Windsurf scan from the repository root with a 30-second timeout to surface TS violations and update the issue log.

Frequently Asked Questions about scan-typescript

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

FAQPage Schema
How do I find TypeScript any usage and ts-ignore violations in my codebase?

To detect TypeScript any usage and ts-ignore violations, run an automated scan that uses ripgrep to identify non-strict patterns. It surfaces problematic constructs across apps and packages directories while deliberately excluding test files to reduce noise.

How do I track static analysis findings for type safety without duplicates?

You can track static analysis findings by appending unique issues to tasks/issues.md. The scanner computes content hashes for each finding to deduplicate results, ensuring your issue log remains clean and tracking progress for post-run review.

Can I integrate TypeScript code quality scanning into a CI pipeline?

You can integrate TypeScript code quality scanning into a CI pipeline because the scan runs with timeout safeguards and produces deterministic results. This reproducible behavior ensures consistent type safety checks across automated runs.

Does the scanner check non-strict TypeScript patterns in test files?

The scanner does not check non-strict TypeScript patterns in test files. It deliberately excludes test files and non-TypeScript files from the ripgrep scan to focus purely on real type safety issues in application and package code.

What is the best way to automate detecting non-strict TypeScript constructs?

The best way to automate detecting non-strict TypeScript constructs is running a scan from the repository root. It identifies problematic patterns like any and ts-ignore, updates the scanner state, and logs findings for post-run review.