verification-guardian

To run lint and typecheck on changed files only, this Skill scopes verification to affected files during IMPLEMENT/EDIT sequences, generating a concise failure report with suggested fixes to minimize resource use on large repositories.

Automated code verification at commit time works by executing lint, scoped typecheck, tests, and custom assertions after code changes, then reporting failures with actionable fixes before merging to ensure code quality.

Yes, you can run scoped tests and lint on low-memory machines because this Skill optimizes resource usage by analyzing only changed or affected files, making it suitable for environments with limited memory like 4GB Chromebooks.

The best way to catch TypeScript errors before merging is to automate verification after edits, running scoped typecheck and custom assertions that report failures with fixes to maintain code quality without heavy resource consumption.

You automate custom assertions and tests by invoking the verification process after write or edit operations, which executes custom assertions alongside lint and typecheck on changed files to produce an actionable failure report.

Scoping typecheck and lint to changed files prevents resource exhaustion on large repositories and low-memory machines, producing a concise actionable report of failures and fixes without running unnecessary full-project checks.