What problem does it solve?
This Skill addresses the gap left by static code review and documentation, which cannot detect runtime-specific issues such as edge cases, undocumented behavior, and common failure modes that only emerge when code is executed, particularly for integrations like the node-redis client.
Core Features & Use Cases
- Structured Validation Matrices: Plans and executes targeted case matrices covering baseline success, edge cases, error scenarios, and repeat-sensitive behavior to ensure high-value, visible coverage.
- Disposable Probe Workflow: Runs temporary TypeScript probe scripts outside git-tracked repository paths to avoid modifying core project files, with strict write-scope guardrails for node-redis projects.
- Findings-First Reporting: Generates reports that prioritize unexpected or negative results, including full runtime context, evidence, and clear scope and confidence markers for each finding.
- Use Case: A node-redis developer can use this Skill to test whether the client correctly handles RESP2 vs RESP3 reply type mapping, or if the offline command queue preserves order after a dropped connection.
Quick Start
Use the runtime-behavior-probe skill to investigate why node-redis returns unexpected reply types when connected to a Redis 8 server using RESP3, and generate a structured validation matrix and findings report for the issue.
