基于 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).