implement-command

Automate new Redis command implementation in the node-redis client library.

17.6k|2.0k|Updated Sep 14, 2010
One-click install
npx skills add https://github.com/redis/node-redis --skill implement-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-command
Source: https://github.com/redis/node-redis/tree/main/.agents/skills/implement-command
Command: npx skills add https://github.com/redis/node-redis --skill implement-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing new Redis commands in the node-redis client library requires following strict repo conventions for command file structure, registration, testing, and validation, which is time-consuming and error-prone for contributors.

Core Features & Use Cases

  • End-to-end command creation: Generates the required TypeScript command file with correct argument parsing and RESP reply transformation logic, following existing repo patterns.
  • Automated registration and testing: Handles JSDoc-compliant registration of both raw and camelCase command aliases in the package index, plus creates co-located tests covering argument serialization and real server/cluster behavior.
  • Use case: Node-redis contributors adding support for new Redis core commands or module commands (JSON, Search, Bloom, Time Series) can use this skill to complete the full implementation workflow without missing required steps or validation checks.

Quick Start

Use the implement-command skill to add support for the Redis HSET command to the @redis/client package, including the command file, index registration, tests, and all required build and validation checks.

Frequently Asked Questions about implement-command

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new Redis commands to the node-redis client library?

To add new Redis commands to node-redis, you must create TypeScript command files with correct argument parsing, register them in the package index with JSDoc-compliant aliases, and set up tests covering argument serialization and cluster behavior.

Can I implement Redis module commands for JSON, Search, Bloom, and Time Series in node-redis?

Yes, implementing Redis module commands for JSON, RediSearch, Redis Bloom, and Time Series in node-redis involves generating command files, registering aliases in the package index, and creating tests following established repo conventions.

What is the best way to ensure test coverage and lint checks pass when implementing Redis commands?

The best way to ensure passing build, lint, and command documentation validation is to follow node-redis repo conventions for RESP reply transformation and create co-located tests covering argument serialization and real server behavior during command implementation.

Why does adding a Redis command to node-redis require JSDoc-compliant index registration?

JSDoc-compliant index registration is required when adding commands to node-redis to properly expose both raw and camelCase command aliases, ensuring the client library correctly parses arguments and transforms RESP replies according to repo conventions.

Does node-redis command implementation support automated argument parsing and RESP reply transformation?

Yes, node-redis command implementation supports automated argument parsing and RESP reply transformation by generating TypeScript command files that strictly follow existing repository patterns for core client and module-specific commands.