Menu
Format, check, test, and commit changes. Use before committing any code changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add a new route to the Arizona router configuration. Use when creating new pages or endpoints.
Scaffold a new Arizona handler module. Ask whether it's a route-level view or an embeddable stateful component.
Trace an event through the full Arizona stack from client click to DOM patch. Use when debugging event handling.
Profile Arizona hot paths with eprof/fprof. Use when investigating performance or picking the next optimization.
Add tests for an Arizona module. Use when creating CT suites, inline EUnit tests, or E2E tests.
Debug Arizona stream operations. Use when investigating stream insert/delete/update/move/sort/reset behavior.
| name | commit |
| description | Format, check, test, and commit changes. Use before committing any code changes. |
| argument-hint | ["commit_message"] |
| allowed-tools | Read, Bash, Grep, Glob |
Prepare and commit the current changes.
Run git diff --name-only and git diff --name-only --staged to capture which files are modified before precommit.
Check the diff from step 1. Only run make precommit if .erl or .js files were touched:
make precommit
If no .erl or .js files changed (e.g. only docs, configs, markdown), skip make precommit.
If it fails, fix the issues and re-run before proceeding. Full CI with E2E is make ci.
Run git diff --name-only again. If make precommit modified files (e.g. formatting changes), show them to the user and ask if they should be included in this commit.
Run git status and git diff to review what will be committed.
If a commit message was provided via $ARGUMENTS, use it. Otherwise, draft a concise message based on the changes.
Stage the relevant files and commit. Do not stage files that contain secrets (.env, credentials, etc.).