OpenParable
Skip to content
← Back to skills

Prepush

Testing & Quality
prepush

Prepush is an Agent Skill for testing & quality published in the starkware-libs/cairo repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Run pre-push checks and Orizi code review for Cairo repository

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/starkware-libs/cairo/blob/HEAD/.claude/skills/prepush/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/prepush, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Context

  • Current directory: !pwd
  • Git status: !git status --short
  • Last commit: !git log --oneline -1
  • Changed files in last commit: !git diff --name-only HEAD~1 HEAD 2>/dev/null || git diff --name-only HEAD

Your task

Perform the following pre-push checks:

  1. 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).

  2. 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.

  3. Review naming: Check the naming of any new functions and classes for good practices (snake_case for functions, CamelCase for types, clear descriptive names).

  4. Orizi review: Use /orizi-review on the changes in the last commit. Fix any issues that can be fixed automatically, and report the rest.

  5. 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.