القائمة
Stage and commit the current changes as a single Conventional Commit that passes this repo's commit-msg rules. Use when the user asks to commit work in OpenWorkspace.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | commit |
| description | Stage and commit the current changes as a single Conventional Commit that passes this repo's commit-msg rules. Use when the user asks to commit work in OpenWorkspace. |
| argument-hint | [optional subject hint] |
| allowed-tools | Bash(git status *) Bash(git diff *) Bash(git add *) Bash(git commit *) Bash(git log *) |
Create one Conventional Commit for the current change set in OpenWorkspace.
git status and git diff --staged (and git diff for unstaged) to see exactly what will be committed. If nothing is staged, stage the intended files with git add — confirm the set is coherent and unrelated changes are left out.main/master. If you are, stop and tell the user to branch first (git checkout -b <type>/<topic>) — the hooks will reject a commit on main anyway.type(scope): subject — type ∈ feat fix docs style refactor perf test build ci chore.domain db auth floorplan crypto i18n notify jobs ui config observability web worker app frontend server) or a cross-cutting scope (ci dev deps release).BREAKING CHANGE: footer or ! after the scope for breaking changes (pre-V1: a breaking change bumps MINOR).git commit -m "..." (and -m again for a body). The local commit-msg hook validates the result; if it rejects, read the message and fix it rather than bypassing.git log -1 --stat.Do not push or open a PR unless explicitly asked.
Scaffold a new workspace crate or app the OpenWorkspace way — edition 2024, inherited lints, thiserror error type, thin facade lib.rs. Use when adding a new member under crates/ or apps/.
Scaffold and apply a sqlx database migration the OpenWorkspace way, then refresh the offline query cache. Use when adding or changing the PostgreSQL schema in crates/db.
Run the full OpenWorkspace quality gate and report pass/fail per check before opening or updating a PR. Use when the user wants to verify a branch is green, or is about to push or open a PR.
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros, closures, observability, testing, and common anti-patterns. Invoke with /rust-skills.