con un clic
con un clic
| 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.
Help with Cairo's file-based golden test framework. Use /golden-tests for creating test runners, writing test files, or fixing test outputs.
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.