3 ファイル変更+7-4
この更新の概要
agent-sdk/pythonの設定にmacOS専用の新しいオプションであるallowMachLookupが追加されました。skillsの定義ルールが更新され、スラッシュコマンド名がYAML内のnameフィールドではなくディレクトリ名に依存するように変更されています。GitHubプルリクエスト上での自動コードレビュー機能とインラインコメントに関する説明が追加されました。全体として、SDKの機能強化と既存スキルの仕様変更を反映した内容となっています。
macOSにおいて特定のXPC/Machサービスへのアクセスを許可するallowMachLookup設定が追加されました。これに伴い、プロパティ一覧のテーブルにデータ型とデフォルト値の説明が追記されています。
@@ -3080,9 +3080,10 @@ class SandboxNetworkConfig(TypedDict, total=False):
allowedDomains: list[str]
deniedDomains: list[str]
allowManagedDomainsOnly: bool
allowLocalBinding: bool
allowUnixSockets: list[str]
allowAllUnixSockets: bool
allowLocalBinding: bool
allowMachLookup: list[str]
httpProxyPort: int
socksProxyPort: int
```
@@ -3092,9 +3093,10 @@ class SandboxNetworkConfig(TypedDict, total=False):
| `allowedDomains` | `list[str]` | `[]` | Domain names that sandboxed processes can access |
| `deniedDomains` | `list[str]` | `[]` | Domain names that sandboxed processes cannot access. Takes precedence over `allowedDomains` |
| `allowManagedDomainsOnly` | `bool` | `False` | Managed-settings only: when set in managed settings, ignore `allowedDomains` from non-managed settings sources. Has no effect when set via SDK options |
| `allowLocalBinding` | `bool` | `False` | Allow processes to bind to local ports (e.g., for dev servers) |
| `allowUnixSockets` | `list[str]` | `[]` | Unix socket paths that processes can access (e.g., Docker socket) |
| `allowAllUnixSockets` | `bool` | `False` | Allow access to all Unix sockets |
| `allowLocalBinding` | `bool` | `False` | Allow processes to bind to local ports (e.g., for dev servers) |
| `allowMachLookup` | `list[str]` | `[]` | macOS only: XPC/Mach service names to allow. Supports a trailing wildcard |
| `httpProxyPort` | `int` | `None` | HTTP proxy port for network requests |
| `socksProxyPort` | `int` | `None` | SOCKS proxy port for network requests |
スラッシュコマンドとして使用される名前の決定方法が、YAML内のnameフィールドからディレクトリ名を参照する方式に変更されました。設定例からnameフィールドの記述が削除され、最新の仕様に合わせて修正されています。
@@ -35,13 +35,12 @@ Create a directory for the skill in your personal skills folder. Personal skills
mkdir -p ~/.claude/skills/explain-code
```
Every skill needs a `SKILL.md` file with two parts: YAML frontmatter (between `---` markers) that tells Claude when to use the skill, and markdown content with instructions Claude follows when the skill is invoked. The `name` field becomes the `/slash-command`, and the `description` helps Claude decide when to load it automatically.
Every skill needs a `SKILL.md` file with two parts: YAML frontmatter (between `---` markers) that tells Claude when to use the skill, and markdown content with instructions Claude follows when the skill is invoked. The directory name becomes the `/slash-command`, and the `description` helps Claude decide when to load it automatically.
Create `~/.claude/skills/explain-code/SKILL.md`:
```yaml theme={null}
---
name: explain-code
description: Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
---
@@ -82,6 +82,8 @@ Progress messages and the live session URL go to stderr so stdout stays parseabl
Running `claude ultrareview` requires the same authentication and extra usage configuration as `/ultrareview`. The subcommand exits with code 0 when the review completes with or without findings, code 1 when the review fails to launch, the remote session errors, or the timeout elapses, and code 130 when interrupted with Ctrl-C. The remote review keeps running if you interrupt the subcommand; follow the session URL printed to stderr to watch it in the browser.
For automatic reviews on GitHub pull requests, [Code Review](/en/code-review) integrates with your repository directly and posts findings as inline PR comments without a CLI step.
## How ultrareview compares to /review
Both commands review code, but they target different stages of your workflow.