← ClaudeAtlas

claude-securitylisted

The Claude Security menu — pick a job: scan the codebase (the whole repository or a scoped part of it), scan changes (this branch's or a pull request's diff, or one commit), or suggest patches (findings turned into targeted patch files, each verified by a panel of agents, that you apply when you choose).
thevibeworks/claude-code-docs · ★ 22 · AI & Automation · score 77
Install: claude install-skill thevibeworks/claude-code-docs
# Claude Security - Session start time (UTC, the stamp report directories are named with): !`date -u +%Y%m%d-%H%M%S` ## The front-desk menu This is the front desk. Its whole purpose is to work out which job the user wants and drive it, following that job's recipe. 1. **If the user already asked for a specific job** — in the arguments (`$ARGUMENTS`) or in plain text ("scan this repo", "scan my branch", "fix the findings", a bare commit sha) — do that job directly and skip the menu. The recipe still asks its own single follow-up question wherever the request left one open. 2. **Otherwise, open with the menu.** Call AskUserQuestion once, single select, `header: "Job"`, `question: "What would you like to do?"`, offering exactly these three options (never invent others — the tool adds its own free-text entry). The menu is your first user-visible act; no text of any kind comes before it. Offer these three options: 1. [Scan codebase](${CLAUDE_SKILL_DIR}/jobs/scan-codebase.md) 2. [Scan changes](${CLAUDE_SKILL_DIR}/jobs/scan-changes.md) 3. [Suggest patches](${CLAUDE_SKILL_DIR}/jobs/suggest-patches.md) "Scan codebase" is the recommended pick — it carries " (Recommended)" and goes first; the other two keep this order. 3. **Then note auto mode once, and Read the chosen job's recipe and follow it.** As soon as the job is known — picked on the menu, or named directly in step 1 — first emit exactly one fixed plain-text line, worded identically every time: "Claude Securi