Menu
Apply CLAUDE:-prefixed comments from a pull request
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | address-comments |
| description | Apply CLAUDE:-prefixed comments from a pull request |
| disable-model-invocation | true |
| allowed-tools | Bash(gh:*), Bash(git:*), Glob, Grep, Read, Edit, Write |
| argument-hint | ["pr-number"] |
Fetch comments from a pull request and apply all comments that are prefixed with "CLAUDE:".
Fetch the PR's comments via gh (see "Fetching comments" below). If a PR number is provided, use it. Otherwise, resolve the current branch's PR with gh pr view --json number.
Parse the output to find all comments (including discussion notes and inline code comments) that start with "CLAUDE:" (case-insensitive).
For each CLAUDE: comment found:
Important restrictions:
Fetch the PR's comments — both inline review comments and general discussion — with gh:
gh api --paginate "repos/{owner}/{repo}/pulls/<N>/comments" — each has .body, .path, and .line (or .original_line). gh substitutes {owner}/{repo} for the current repo.gh api --paginate "repos/{owner}/{repo}/issues/<N>/comments".If a PR number was provided, use it; otherwise resolve the current branch's PR with gh pr view --json number.
Important: the comment JSON can be large and may get truncated — save it to a temp file first, then parse with jq in a separate command (not chained with &&) to avoid shell-parsing issues with the jq expression.
From the fetched comments, select those whose body starts with "CLAUDE:" (case-insensitive). For each, capture the body and — for inline comments — the file path and line. GitHub's REST comments have no resolved flag, so rely on the diff to see what's already done.
For each CLAUDE: comment:
Summarize all changes made at the end.
Build 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.