القائمة
Use when asked to independently review Claude-authored docs or code changes, Claude-generated diffs, or Claude PR work in the Redis docs repo.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/redis/docs --skill claude-reviewيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Create or extend tabbed code examples (TCEs) — the multi-language code blocks rendered by the clients-example shortcode. Use when a docs page needs client examples added, when auditing a command page for missing client coverage, when an example set needs a new step, or when a client needs backfilling into an existing set. Covers audit, parallel generation across clients, live testing, and Codex review.
Port a Redis use-case example (cache-aside, session store, rate limiter, leaderboard, etc.) to all 9 supported client libraries in parallel, with cross-client synthesis and audit
Score a community Redis client library against the docs team's quality checklist. Use when reviewing a PR or suggestion to add a client library to the redis.io clients page, or when asked to vet/evaluate a Redis client library.
| name | claude-review |
| description | Use when asked to independently review Claude-authored docs or code changes, Claude-generated diffs, or Claude PR work in the Redis docs repo. |
Use this skill for independent reviews of Claude-authored work in this repo. The goal is to find real correctness, docs, consistency, test, and maintainability issues without becoming biased by past Claude behavior.
Read these before reviewing:
references/review-style.md for output format and severity.references/claude-review-patterns.md for recurring review patterns.If the change touches tabbed code examples — local_examples/, a client repo's doctests,
data/examples.json, the client config in config.toml, or
.claude/skills/tce-examples/ — also read
references/tce-review-patterns.md. Those defects mostly
survive a green test run, so the test result is not the review.
Treat the pattern file as a map of places to inspect, not as evidence. The current diff and current workspace always win.
git diff, git status --short, and the touched files before judging.claude-review-patterns.md as a targeted checklist:
At the end of a review, add a short Suggested skill-memory updates section only if the review revealed a reusable pattern that is:
references/claude-review-patterns.md.Suggest the update text, but do not apply it unless explicitly asked. New entries should follow the schema in claude-review-patterns.md.