القائمة
Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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 to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
深度调研方法论（8步法）：将模糊主题转化为高质量调研报告。 触发词：/deep-research、深度调研、帮我调研、调研一下、对比分析 注意：如果用户需要的是可视化图谱而非报告，请使用 research-to-diagram skill。
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
Seedance 2.0 video & image generation via LibTV Gateway - AI text-to-video, image-to-video, video continuation, style transfer, and text-to-image using Seedance 2.0 model. Also supports Kling 3.0, Wan 2.6, Midjourney, Seedream 5.0. Trigger phrases: seedance, generate video, make a video, generate image, make an image, draw, libtv, liblib.
All-in-one image generation with Gemini models. Supports Nano Banana (3.1 Flash), Nano Banana Pro (3 Pro), and Nano Banana 2 (2.5 Flash). Triggers on "generate image", "image generation", "nano banana", "edit image".
استنادا إلى تصنيف SOC المهني
| name | sync-specs |
| description | Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation. |
Review code changes and update project documentation for consistency.
| Mode | How to activate | Behavior |
|---|---|---|
delta (default) | No argument, or say "delta" | Diff against merge-base with origin/main + working tree changes |
full | Say "full audit" or "full sync" | Complete audit of all docs against current codebase |
| Scope keyword | Say the keyword (e.g. "db", "api") | Targeted check (see Scope Filters below) |
Identify changed files using merge-base (not a fixed commit count):
# Branch changes since diverging from main
git diff --name-only $(git merge-base HEAD origin/main)...HEAD
# Plus staged + unstaged
git diff --name-only --cached
git diff --name-only
Combine the results into a single list of changed files. Then use the Impact Mapping to identify which docs may need updates.
Map changed areas to the docs they affect:
| Changed area | Affected docs |
|---|---|
apps/controller/src/routes/ | specs/references/api-patterns.md, ARCHITECTURE.md, specs/product-specs/*.md (if route is user-facing) |
apps/web/src/pages/ or apps/web/src/app.tsx | specs/FRONTEND.md |
apps/landing/ | ARCHITECTURE.md (Monorepo layout) |
apps/controller/src/runtime/ | ARCHITECTURE.md, specs/RELIABILITY.md |
packages/shared/src/schemas/ | ARCHITECTURE.md (Type safety) |
package.json scripts | CLAUDE.md + AGENTS.md Commands sections |
| New apps/packages dirs | ARCHITECTURE.md (Monorepo layout) |
| Config generator | specs/references/openclaw-config-schema.md, specs/openclaw-config-reference.md |
| Auth changes | specs/SECURITY.md |
| New/moved doc files | CLAUDE.md Doc Map, AGENTS.md Where to look, relevant index files |
Always verify consistency between these paired docs:
CLAUDE.md Commands section <-> AGENTS.md Commands section (same entries)CLAUDE.md Documentation Map paths <-> actual files on diskCLAUDE.md Hard Rules <-> AGENTS.md Hard rulesARCHITECTURE.md monorepo layout <-> actual apps/ + packages/ dirsspecs/DESIGN.md table <-> actual specs/design-specs/ + specs/designs/ contentsspecs/design-specs/index.md table <-> actual design filesspecs/product-specs/index.md table <-> actual specs/product-specs/*.md filesspecs/PLANS.md table <-> specs/exec-plans/{active,completed}/ contentsspecs/FRONTEND.md Pages table <-> apps/web/src/app.tsx routesWhen the user specifies a scope keyword, limit the check to that area:
| Keyword | What it checks |
|---|---|
db | Schema source vs specs/generated/db-schema.md |
api | Route files vs specs/references/api-patterns.md |
frontend | apps/web/ vs specs/FRONTEND.md |
commands | package.json scripts vs CLAUDE.md/AGENTS.md Commands sections |
architecture | All apps/ + packages/ vs ARCHITECTURE.md layout |
security | Auth/crypto code vs specs/SECURITY.md |
links | Verify all doc map paths and index references resolve to existing files |
guides | specs/guides/** internal cross-references |
designs | specs/designs/** + specs/design-specs/** vs index files |
exec-plans | specs/exec-plans/** vs specs/PLANS.md |
product-specs | specs/product-specs/** vs index + specs/PRODUCT_SENSE.md |
apps/controller as the source of truth; do not reference removed legacy package paths.CLAUDE.md <-> AGENTS.md consistency after any update to either file.