菜单
Alias for /update-docs (knowhow branch). Use when user says '记下来', '归档', 'save this', or after a <knowhow-hint> prompt. Routes to the unified /update-docs workflow with knowhow branch auto-selected.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Unified document archival — covers both agent-facing knowhow (env setup, debug, infra, runbooks) and human-facing docs (design, guides, README, changelog). Triggers on: "update docs", "更新文档", "写 README", "记下来", "归档", "save this", "update knowhow", or after a <knowhow-hint> prompt. Also triggers when conversation context implies documentation should be created or updated.
Use when an experiment has completed and results need analysis, interpretation, or presentation. Triggers on "analyze results", "分析实验", "interpret experiment", "what did exp find", "run analysis".
Use when creating git commits, updating CHANGELOG.md, committing across nested repos, or generating weekly progress summaries. Triggers on "commit", "提交", "changelog", "weekly summary", "周报", "write commit message".
Use when setting up a new project (general or research) or when .pipeline-state.json is missing. Triggers on "init project", "初始化项目", "set up labmate", "first time setup", "initialize".
Check experiment status and diagnose failures via exp-manager. Triggers on "check status", "看看实验", "how's the run", "any failures", "is it done", "monitor experiment", "experiment status".
Use when starting a new experiment — scaffolds exp/{exp_id}/ directory with README, config, run.py, analyze.py, and results structure. Triggers on "new experiment", "新实验", "scaffold exp", "set up experiment", "create experiment".
| name | update-knowhow |
| description | Alias for /update-docs (knowhow branch). Use when user says '记下来', '归档', 'save this', or after a <knowhow-hint> prompt. Routes to the unified /update-docs workflow with knowhow branch auto-selected. |
| disable-model-invocation | true |
This is an alias. Execute /update-docs — it will auto-route to Branch A (knowhow) based on context.
All logic lives in /update-docs. Do not duplicate workflow here.
