القائمة
Pre-commit gate (format + lint + test) then create a conventional commit with explicit file staging.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review a pull request or pending changes. Performs a focused code review against the current branch's diff (or staged diff if invoked pre-commit), surfacing correctness bugs, missing tests, style violations, and unclear naming. Use when the user asks to "review this", "review the PR", "code review", or before commits/PRs.
Complete a security review of pending changes on the current branch. Focuses on injection, authn/authz, secrets, SSRF, deserialisation, insecure defaults, and supply-chain risk. Use when the user asks to "security review", "security audit", "check for vulns", or before raising a PR.
Pre-commit gate (fmt + clippy + test) then create a conventional commit with explicit file staging.
Create or update ARCHITECTURE.md with system components, data flows, and ADRs
Format Rust code with rustfmt and report what changed.
Full TDD loop — plan, branch, write code + tests, fmt, clippy, test, review, commit.
| name | commit |
| description | Pre-commit gate (format + lint + test) then create a conventional commit with explicit file staging. |
The enforcer. Nothing reaches the index without passing the gate.
1. Format check.
swift format --recursive Sources Tests --in-place
Then stage any formatting changes:
git add -u Sources Tests
2. Lint check.
swift format lint --recursive Sources Tests
If any violations: fix them. No // swiftlint:disable suppression without a comment explaining why it's a confirmed false positive. Re-run until exit 0.
3. Full test run.
swift test 2>&1
Must pass. If it fails: halt. Surface the failure.
4. Code review against staged changes.
git diff --cached
Run code review per .nidex/skills/review/SKILL.md. Apply findings. If any fix was applied, loop back to step 1. Max 2 loops, then escalate.
5. Stage files explicitly.
git add <file1> <file2> ...
Never git add -A or git add .. Use git status --short to enumerate what's staged. If something unintended shows up (e.g. Package.resolved changes you didn't intend), ask the user.
6. Compose the commit message. Conventional commits format:
<type>(<scope>): <short imperative description>
<optional body — wrap at 72 cols, explain WHY not WHAT>
Types: feat, fix, chore, test, docs, refactor, perf, style, build, ci.
Rules: imperative mood, <= 72 char subject, no emoji.
7. Commit.
git commit -m "$(cat <<'EOF'
<message>
EOF
)"
8. Confirm.
git log -1 --oneline
git status --short
If a pre-commit hook fails: the commit did not happen. Fix the issue, re-stage, and create a new commit. Never --amend after a hook failure.