بنقرة واحدة
commit
Run pre-commit checks (fmt, clippy, test) then stage, commit, and push with a conventional message
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Run pre-commit checks (fmt, clippy, test) then stage, commit, and push with a conventional message
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Deep codebase analysis — architecture health, test coverage gaps, tech debt, and actionable findings
Review staged or recent changes for correctness, style, and Rust conventions before committing
Use when SSHing into remote machines, looking up credentials, renaming Tailscale devices, or accessing services on the tailnet. Symptoms - SSH auth failures, too many authentication failures, command not found tailscale, need to find credentials for remote machines.
Use when mixing Tokio async code with synchronous blocking I/O libraries (tar, flate2, zip, csv), or when seeing "cannot block the current thread from within the async context" panics, or needing to stream async bytes into a sync reader.
Structured BAML schema edit → validate → test loop for the devloop project. Use when editing any *.baml file in crates/baml/baml_src/ — covers version parity gotchas, uvx invocation, regeneration workflow, and the analyze verify step.
Use when reading large files (logs, JSONL, CSVs) that exceed context limits, when the Read tool returns truncated output, or when needing to locate a specific section in a multi-thousand-line file without reading everything.
| name | commit |
| description | Run pre-commit checks (fmt, clippy, test) then stage, commit, and push with a conventional message |
| trigger | /commit |
| tags | ["git","rust","workflow"] |
Run pre-commit quality gates, then commit and push.
If in a Rust workspace, run in order — stop and report if any fail:
cargo fmt --allcargo clippy --all-targets -- -D warningscargo test --quiet (or cargo nextest run if nextest is available)Run git status to identify changed files. Stage only relevant files (not secrets, .env, large binaries).
Run git diff --staged to review what's being committed.
Write a conventional commit message:
<type>(<scope>): <description>feat, fix, refactor, chore, docs, testCommit with Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> trailer.
Push to the current branch's remote tracking branch.
Report the commit hash and pushed ref.
--no-verify..env files, secrets, or *.local.* files.