ts-quality

# TypeScript Quality Enforcement

This skill helps maintain TypeScript code quality by running instant checks on each file after it's written or modified.

## What This Skill Does

When activated, this skill ensures TypeScript code meets quality standards by:

1. **Type Checking** - Runs `pnpm exec tsc --noEmit <file>` to ensure zero TypeScript type errors
2. **Linting** - Runs `pnpm lint <file>` to enforce code style consistency

Checks run on the SPECIFIC FILE that was just written/modified, not the entire project.

## When to Use This Skill

Activate this skill:

- **Immediately after writing or modifying any .ts or .tsx file**
- After creating new TypeScript files
- After editing existing TypeScript files
- When user mentions: "quality checks", "typecheck", "lint", "validate code"
- Before creating git commits
- During code review processes

## Quality Standards

**ZERO TOLERANCE POLICY**: No lint errors or type errors are acceptable.

### Required Checks (in sequence):

1. **Type Checking** - File-scoped typecheck
   - Must pass with zero errors
   - Validates TypeScript type safety for the specific file

2. **Linting** - File-scoped lint
   - Must pass with zero errors
   - Enforces consistent code formatting and style

## Instructions

When this skill is active, follow these steps:

### 1. Announce Activation

Immediately inform the user that quality checks are running:

```
🔍 Checking {filename}...
```

Replace `{filename}` with the actual file path (e.g., `src/utils/auth.ts`).

### 2. Identify the File to Check

Determine which TypeScript file was just written or modified. This is the file to check.

### 3. Run File-Scoped Quality Checks

Execute checks sequentially on the SPECIFIC FILE ONLY:

```bash
# Type check the specific file
pnpm exec tsc --noEmit path/to/file.ts

# Lint the specific file
pnpm lint path/to/file.ts
```

**Important**:
- Only check the file that was written/modified
- Do NOT run project-wide checks
- Each command must succeed before t