菜单
Apply a unified diff to the workspace. Use when: the user provides a patch, you generated a diff and want to apply it, or you're integrating an upstream change. NOT for: small surgical edits to a known file (use file-ops write_file).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
Drive a real browser via Playwright for tasks that need JavaScript execution, login forms, or interactive UI. Use when: scraping a SPA, filling out a form, taking a screenshot, downloading from a JS-protected page, or running an end-to-end check. NOT for: static HTML (use web_fetch), public APIs (use curl), or anything where a simple HTTP GET works.
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.
Delegate coding tasks (build features, refactor, batch PR reviews, parallel issue fixes via Codex/Claude Code/Pi/OpenCode) by spawning the `coding-agent` sub-agent. Use when: (1) the work needs file exploration + multi-step edits, (2) you want a separate process so its tool noise stays out of your context, (3) you need parallel coding sessions. NOT for: simple one-liner edits (just edit), reading code (use read tools), thread-bound ACP requests (use sessions).
Read, write, and search files in the workspace. Use when: the user asks to inspect, modify, create, or search files; you need to find code by name or content. NOT for: running scripts (use shell-exec), pulling remote URLs (use web_fetch), or pdf/image content (use the pdf/image plugins).
| name | apply-patch |
| description | Apply a unified diff to the workspace. Use when: the user provides a patch, you generated a diff and want to apply it, or you're integrating an upstream change. NOT for: small surgical edits to a known file (use file-ops write_file). |
| metadata | {"all_agents":{"emoji":"🩹","requires":{"bins":["patch"]}}} |
Use the run_command infra capability to invoke GNU patch -p1.
write_file { path: "patches/change.diff", content: "..." }.run_command { command: "patch -p1 < patches/change.diff" }..rej files via glob_files { pattern: "*.rej" }.read_file the target paths first to confirm context lines match.patch won't apply them.run_command if available.