← ClaudeAtlas

ran-bar-ziklisted

Security code review against Ran Bar-Zik's ten commandments. סקירת אבטחת-קוד לפי "עשרת הדיברות" של רן בר-זיק. Trigger when the user runs /ran-bar-zik (with or without arguments), or asks: "security review", "review this for security", "check for XSS", "check for IDOR", "is this secure", "audit this endpoint", "סקירת אבטחה", "בדוק אבטחה", "האם זה בטוח" - and before any merge/deploy of code touching auth, authorization, user input, file upload, or personal data. Subcommands: fix, xss, idor, secrets, deps, privacy, llm, harden, explain, checklist, community. Do NOT use for CVE/dependency scanning or regulatory compliance (use israeli-appsec-scanner), nor for general correctness/bug review (use code-review). Hebrew companion: SKILL_HE.md.
ShachTzu/ran-bar-zik-security-skill · ★ 1 · Code & Development · score 65
Install: claude install-skill ShachTzu/ran-bar-zik-security-skill
# Ran Bar-Zik's Ten Commandments - Security Reviewer Run a security code review against the ten commandments. Guiding principle: **"the browser is the attacker's tool"** - anything sent to the client is visible and editable in F12. (Hebrew version: `SKILL_HE.md`.) **Language:** write the report in the user's language. If the user writes in Hebrew, the whole report is in Hebrew, including field names and commandment names. Don't mix languages. ## Step 1 - pick a target `/ran-bar-zik` **always reviews something**. Don't ask "what should I review?" before trying to find it yourself. Argument given? That's the target: a file/dir path · `pr <n>` (run `gh pr diff <n>`) · sha/branch (run `git diff <ref>`) · a pasted snippet · `all`/`repo` for the whole codebase. **No argument? Go in this order and stop at the first that returns something:** 1. `git diff` - uncommitted changes. 2. `git diff main...HEAD` (or `master`) - the branch diff. 3. The project's sensitive files: routes/endpoints, auth, models, forms, config. Only if all three are empty and nothing was pasted - ask the user to point at something. ## Step 2 - scan for red flags Locate `scan.sh` and run it against the target. The path isn't known up front - search for it: ```bash SCAN=$(ls ~/.claude/skills/ran-bar-zik/scripts/scan.sh \ .claude/skills/ran-bar-zik/scripts/scan.sh 2>/dev/null | head -1) [ -n "$SCAN" ] && bash "$SCAN" <path> # or: bash "$SCAN" --diff [ref] ``` Not found? Run `find ~/.clau