safe-local-checkslisted

# Safe local checks Use this skill only when a bounded local static, syntax, or explicit Node test-file check would give useful feedback. Builds, package test scripts, type checks, dependency-graph analysis, installs, servers, and watch processes remain CI-only. ## When it is useful - After editing JavaScript modules, run `syntax` to catch parser errors quickly. - After editing TypeScript or TSX, run `ts-syntax` on the touched files when repo-local `esbuild` is already installed. - After editing JSON, YAML, shell scripts, package locks, or Pi preseed files, run the matching parse or consistency mode. - Run explicit Node unit-test files when focused behavioral feedback is needed. - Run a repository-installed analyzer on changed paths, or its full-project read-only scope, before pushing when lint feedback would help. - Do not use this capability for package test scripts, broad integration tests, builds, type checks, Knip, final verification, or dependency installs; those belong to CI. ## Managed runner Run the seeded wrapper from the repository being checked. The selected analyzer must already be installed by that repository in `node_modules/.bin`; if it is absent, do not install it locally—report that the check is unavailable and rely on CI. Parse and consistency modes never download packages. ```bash node ~/.claude/skills/safe-local-checks/scripts/safe-local-check.mjs oxlint [paths...] node ~/.claude/skills/safe-local-checks/scripts/safe-local-check.mjs eslint [paths...