菜单
Verify moon command behavior matches Redis exactly. Args: command name(s) or --category <name>. Uses redis-cli against both servers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
ADD (AI-Driven Development) — a minimal, state-tracked workflow for building software where the AI writes the code and the human owns direction and verification. Drives every feature through one lean TASK.md: Specify → Scenarios → Contract → Tests → Build → Verify → Observe, with red/green TDD built in. Use this skill whenever working in a repo that has a `.add/` directory, when the user says "add", "start a task", "next phase", "specify this feature", "ADD method", or "AI-driven development", or when scaffolding a new feature and you want spec/tests-first discipline instead of vague-prompt coding. Also use it to resume work across sessions (it reads `.add/state.json` so you never re-read the whole repo).
Scaffold a new Redis command implementation with dispatch entry, handler, ACL, tests, and consistency test entry. Args: COMMAND_NAME [category].
Scan hot-path code for allocation violations, lock misuse, and performance anti-patterns. Zero-tolerance audit.
Scaffold a new CUDA kernel with Rust integration via cudarc. Args: kernel_name [f32|f16]. Creates .cu kernel, Rust wrapper, CPU fallback, and benchmark.
Verify code compiles and tests pass under both runtime-tokio and runtime-monoio feature sets. Run before committing runtime-adjacent changes.
Benchmark GPU-accelerated operations (vector distance, batch computation) against CPU baselines. Requires CUDA toolkit. Args: vector|distance|batch|all.
| name | redis-compat |
| description | Verify moon command behavior matches Redis exactly. Args: command name(s) or --category <name>. Uses redis-cli against both servers. |
Redis compatibility checker for moon commands.
/redis-compat GETRANGE SETRANGE — check specific commands/redis-compat --category string — check all string commands/redis-compat --all — check all implemented commandsStart Redis server and Moon server on different ports:
redis-server --port 6399 --daemonize yes
cargo build --release --no-default-features --features runtime-tokio,jemalloc
./target/release/moon --port 6400 &
For each command, run identical operations against both servers via redis-cli:
Compare response bytes character-for-character.
Use context7 to fetch latest Redis docs for edge case behavior.
Report per command: [COMPATIBLE|DIVERGENT|UNTESTED] with specific divergences.
Cleanup:
redis-cli -p 6399 SHUTDOWN NOSAVE
redis-cli -p 6400 SHUTDOWN NOSAVE
string, list, hash, set, sorted_set, key, stream, connection, pubsub, transaction, scripting, persistence