Skill: Workspace Lint

Goal

Lint affected TypeScript and markdown files across the workspace using Nx affected detection, with a full-run fallback available.

Use This Skill When

• You need to verify code quality across multiple repositories
• You are about to commit changes and want to ensure lint compliance
• You want to check for common ESLint violations before pushing

Do Not Use This Skill When

• You are only working in a single submodule and can run its own lint
• The change is unrelated to TypeScript or markdown files

Inputs

• File paths to lint (default: affected files from git working tree + staged + untracked)
• Lint options (if any from workspace scripts)