Code Change Verification

Use this skill to choose the smallest credible validation set for an ioredis change, run it when feasible, and report exactly what passed, failed, or was skipped.

Workflow

1. Inspect the diff and changed files before choosing commands.

   • Use git diff --stat, git diff --name-only, and targeted file reads.
   • Do not stage, unstage, or commit unless the user explicitly asks.
   • Treat built/ and lib/utils/RedisCommander.ts as generated outputs; do not hand-edit them.

2. Classify the change.

   • Runtime code under lib/: run focused tests plus build when the change affects exported declarations or compiled output.
   • Redis command typing or generated command support: inspect bin/ config, regenerate with node bin/index.js if needed, and run tsd or targeted typing tests.
   • Functional Redis behavior: run the smallest relevant Mocha files and assume a compatible Redis server is on default host/port. If sandboxed Redis access is blocked, ask for permission rather than assuming Redis is unavailable.
   • Cluster behavior: use npm run docker:setup if infrastructure is needed, then targeted test/cluster/**/*.ts or npm run test:cluster.
   • Docs-only changes: run npm run format-check only if formatting-sensitive files changed; otherwise inspect rendered Markdown manually.
   • Build/tooling changes: run npm run build and the affected script directly.