القائمة
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/starkware-libs/cairo --skill prepushيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | prepush |
| description | Run pre-push checks and Orizi code review for Cairo repository |
| allowed-tools | Bash(.claude/skills/prepush/pre_push.sh:*), Bash(./scripts/rust_fmt.sh:*), Bash(./scripts/clippy.sh:*), Bash(./scripts/docs.sh:*), Bash(typos:*), Bash(taplo:*), Bash(cargo machete:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(cargo fmt:*), Bash(cargo clippy:*), Read, Glob, Grep |
pwdgit status --shortgit log --oneline -1git diff --name-only HEAD~1 HEAD 2>/dev/null || git diff --name-only HEADPerform the following pre-push checks:
Run pre_push.sh: Execute .claude/skills/prepush/pre_push.sh and ensure no errors exist. If there are errors, fix them by running the appropriate fix commands (e.g., ./scripts/rust_fmt.sh for formatting, cargo clippy --fix --allow-dirty for clippy warnings, typos -w for typos).
Analyze changes: Look at the changes in the last git commit and current diff to identify any missing documentation on public functions or non-trivial inner functions.
Review naming: Check the naming of any new functions and classes for good practices (snake_case for functions, CamelCase for types, clear descriptive names).
Orizi review: Use /orizi-review on the changes in the last commit. Fix any issues that can be fixed automatically, and report the rest.
Provide a minimal report: Summarize any fixes made and provide suggestions for where fixes are still needed, including Orizi review findings.
Focus on being thorough but concise. Fix what you can automatically, and report what needs manual attention.
Code review in the style of Ori Ziv (orizi). Reviews for correctness, simplicity, clean code, and performance. Catches unnecessary complexity, redundant code, naming issues, and architectural concerns. Use /orizi-review [file or PR] to review changed code.
Use when writing or changing tests in this repo, deciding what to test or where a test belongs, adding a regression test for a bug fix, reviewing the test portion of a PR, deciding which golden outputs to bless and reviewing the blessed diff, or adding a benchmark. Trigger phrases include "add a test", "write tests for", "is this covered", "does this need a test", "review the tests here", "which layer should this test go in". Also use for the mechanics of the golden framework itself — the //! > file format, creating test_file_test! runners, or how CAIRO_FIX_TESTS works (covered in references/golden-framework.md).