القائمة
You want other AI models to critique a plan before you build it. Cross-AI peer review
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-reviewيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Something was built and you want tests covering what it promised to do
A step involves building an AI system and you want its design and evals pinned down first
You want issues found, classified, fixed, tested and committed without steering each one
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | ferrox-review |
| description | You want other AI models to critique a plan before you build it. Cross-AI peer review |
| argument-hint | --phase N [--gemini] [--claude] [--codex] [--opencode] [--qwen] [--cursor] [--agy] [--all] |
| allowed-tools | ["Read","Write","Bash","Glob","Grep"] |
Flow: Detect CLIs → Build review prompt → Invoke each CLI → Collect responses → Write REVIEWS.md
<execution_context> @~/.claude/ferrox-core/workflows/review.md </execution_context>
Phase number: extracted from $ARGUMENTS (required)Flags:
--gemini — Include Gemini CLI review--claude — Include Claude CLI review (uses separate session)--codex — Include Codex CLI review--opencode — Include OpenCode review (uses model from user's OpenCode config)--qwen — Include Qwen Code review (Alibaba Qwen models)--cursor — Include Cursor agent review--agy / --antigravity — Include Antigravity CLI review--all — Include all available CLIsNo flags — if review.default_reviewers is set, review with only those configured
reviewers that are detected; otherwise review with all available CLIs. Configured
review.reviewer_instances names may appear in review.default_reviewers; each runs as an
independent reviewer identity backed by its configured adapter+model (see
docs/CONFIGURATION.md). Instance names are not valid as flags.