菜单
Run Claude programmatically against collections of files in the codebase. Use for batch analysis: scrubbing sensitive data, auditing style violations, security reviews.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | batch-claude-runner |
| disable-model-invocation | true |
| description | Run Claude programmatically against collections of files in the codebase. Use for batch analysis: scrubbing sensitive data, auditing style violations, security reviews. |
Runs Claude against batches of files, collecting structured findings into a summary report.
# Basic usage
python .claude/skills/batch-claude-runner/scripts/batch_claude_runner.py \
--pattern "**/*.py" \
--prompt "Check for hardcoded credentials or API keys."
# See all options
python .claude/skills/batch-claude-runner/scripts/batch_claude_runner.py --help
--pattern / -p: Glob pattern for files (required, repeatable)--exclude / -e: Exclude pattern (repeatable)--prompt: Analysis prompt--batch-size / -b: Files per batch (default: 10)--max-batches / -m: Limit batches (for testing)--dry-run: Preview files without running--output json: Machine-readable output--json-schema--dry-run first to verify file selectionBuild or modify a Sculptor extension — a runtime ESM module loaded into the Sculptor UI. Use when asked to write an extension (or "plugin") for Sculptor, add a panel, overlay, workspace widget, home view, or settings UI to Sculptor, or to iterate on an extension with `sculpt extension`. Works from any repo; this file is a self-contained reference (the Sculptor source code is optional).
Interact with Sculptor programmatically using the sculpt CLI. Use this skill when using `sculpt`, or when designing or planning a workflow that would benefit from understanding the structural capabilities of `sculpt` (workspaces, agents, isolation, and how code flows between them).
Live, hot-reloading preview of the Sculptor WEB frontend from a phone or any browser, served through the OpenHost nginx /proxy front. ONLY relevant when running INSIDE the openhost-deployed Sculptor (the container fronted by nginx on :5050, reachable at https://sculptor.<zone>/) — NOT for local or Electron dev. Frontend-only: it reuses the single shared backend, so it previews UI/frontend changes, not a per-workspace backend. Invoke when iterating on the web UI and wanting to see it live in a browser through the OpenHost SSO front.
How this OpenHost-hosted Sculptor environment works — storage and what survives restarts, where/how to add repositories and authorize gh, and the /proxy/<port>/ capability for previewing loopback web apps from a browser. ONLY relevant when running inside an OpenHost deployment (detect via the OPENHOST_* env vars, e.g. OPENHOST_APP_NAME). Ships with the deploy image and is refreshed every release.
Test a pull request by creating a shallow clone at the PR's commit and launching Sculptor. Use when you need to test changes from a specific PR in isolation.
QA the Sculptor mobile web UI on a real iOS Simulator, driven headlessly from a Mac. A single CLI boots a notched iPhone, launches the local frontend server (parsing its port — no hardcoding), opens the app in MobileSafari, taps/swipes via idb, and screenshots each step. Includes the Add-to-Home-Screen standalone flow — the only way to verify notch / status-bar / home-indicator safe-area rendering (env(safe-area-inset-*) is 0 everywhere except real iOS). Use when visually verifying mobile/responsive changes on an iPhone.