MCPInstall

auto-type-checking

Run TypeScript type checking after file edits and immediately flag type errors before moving on. Uses Cursor hooks for automatic enforcement.

Installs
438
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill auto-type-checking
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads auto-type-checking automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Auto Type Checking

Catch type errors immediately after every edit instead of discovering them at build time.

Manual Workflow

After editing a TypeScript file, run:

npx tsc --noEmit 2>&1 | head -30

If errors appear, fix them before moving on.

Automated with Cursor Hooks

Add to .cursor/hooks.json to run automatically after every file edit:

{
  "hooks": [
    {
      "event": "afterFileEdit",
      "script": "check-types.sh",
      "pattern": "**/*.{ts,tsx}"
    }
  ]
}

Create .cursor/hooks/check-types.sh:

#!/bin/bash
# Quick type check — only reports errors, doesn't block
npx tsc --noEmit --pretty 2>&1 | head -20
exit 0  # Don't block the agent even if there are errors
chmod +x .cursor/hooks/check-types.sh

What to Check

When type errors appear:

  1. Missing imports: Cannot find name 'X' → add the import
  2. Type mismatches: Type 'string' is not assignable to type 'number' → fix the type or the value
  3. Missing properties: Property 'x' does not exist on type 'Y' → add the property to the interface or fix the access
  4. Null safety: Object is possibly 'null' → add null check or optional chaining
  5. Generic constraints: Type 'X' does not satisfy the constraint 'Y' → fix the generic parameter

Tips

  • Use --noEmit to type-check without producing output files
  • For large projects, tsc can be slow — consider --incremental or running only on changed files
  • If using path aliases, ensure tsconfig.json paths are configured correctly
  • For monorepos, run tsc from the package root, not the workspace root
  • Pair with grinding-until-pass for a full "fix until clean" loop

FAQ

What does the auto-type-checking skill do?

Run TypeScript type checking after file edits and immediately flag type errors before moving on. Uses Cursor hooks for automatic enforcement.

How do I install auto-type-checking?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill auto-type-checking in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/auto-type-checking/ (personal) or .claude/skills/auto-type-checking/ (project).

Which AI agents can use auto-type-checking?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is auto-type-checking safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains auto-type-checking?

It is published by spencerpauly in spencerpauly/awesome-cursor-skills. It has 438 recorded installs.

More from spencerpauly/awesome-cursor-skills

View all →

visual-qa-testing

spencerpauly/awesome-cursor-skills

Visually QA a web application by launching it in Cursor's built-in browser, taking screenshots, checking console errors, and auditing network requests. Use after making UI changes to verify they look correct.

Testing & QA648 installs

auditing-security

spencerpauly/awesome-cursor-skills

Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.

Security598 installs

responsive-testing

spencerpauly/awesome-cursor-skills

Open the app in Cursor's browser at multiple viewport sizes, screenshot each, and report any layout breakage.

Testing & QA569 installs

suggesting-cursor-rules

spencerpauly/awesome-cursor-skills

When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.

559 installs

systematic-debugging

spencerpauly/awesome-cursor-skills

Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.

grinding-until-pass

spencerpauly/awesome-cursor-skills

Keep iterating on code changes until the tests pass, the build succeeds, or linting is clean. Runs in a tight loop of fix → run → check → repeat. Use when you want the agent to autonomously grind through test failures or build errors.

Testing & QA551 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.