菜单
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".
用 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.
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.
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 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 | commit-changelog |
| description | 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". |
| disable-model-invocation | true |
<type>(scope)?: <summary>
- what changed
- impact: <module/behavior>
- verification: <cmd or note>
| Type | 用途 | Type | 用途 |
|---|---|---|---|
feat | 新功能 | fix | Bug 修复 |
docs | 文档 | refactor | 重构 |
test | 测试 | chore | 构建/工具链 |
perf | 性能 | build | 构建系统 |
Breaking change: feat!: <summary>
## vX.Y.Z @author - YYYY-MM-DD
### 新增
### 变更
### 修复
### 构建与工具链
### 其他
MUST commit in BOTH repos, inner first:
1. Inner repo (nested): commit + push
2. Outer repo (parent): commit (references inner change) + push
| 变更位置 | Inner commit | Outer commit |
|---|---|---|
| Only inner files | Yes | Only if submodule pointer needs updating |
| Only outer files | No | Yes |
| Both repos | Yes (first) | Yes (second, reference inner) |
| Inner is gitignored | Yes (independent) | Describe inner changes in outer message |
When invoked as /commit-changelog --weekly or when user asks for a weekly summary:
Determine week range:
docs/weekly/YYYY-WNN.md already exists (append mode if so)Gather data from real files (never fabricate):
a. CHANGELOG.md — entries since last weekly (or all if first)
b. git log — git log --oneline --since="7 days ago" for commit history
c. exp/summary.md — experiment status changes
d. exp/*/README.md — any new findings sections populated
e. .pipeline-state.json — current stage and experiment
Write structured summary to docs/weekly/YYYY-WNN.md:
# Weekly Progress — Week {NN} ({date_range})
## Overview
One paragraph summarizing the week's main achievements.
## Key Changes
(from CHANGELOG.md + git log, grouped by type: Features / Fixes / Docs)
## Experiments
| Exp | Status | Change This Week |
|-----|--------|-----------------|
## Next Week
(inferred from pipeline state + TODOs in exp READMEs)
Prompt user: "Review the weekly summary, then commit? (Y/n)"