ReSoul
Reset the workspace bootstrap state so the next fresh session can start from the official upstream BOOTSTRAP.md.
Primary workflow
- 1. Warn that running
resoul will fetch the official BOOTSTRAP.md, then archive the current SOUL.md, USER.md, and IDENTITY.md into .trash/ and remove them from the workspace root if they exist. - Require an explicit second confirmation before executing anything. Do not treat vague replies like "ok" or "继续" as sufficient; require a clear confirmation that the user agrees to archive and remove the current
SOUL.md, USER.md, and IDENTITY.md from the workspace root. - Fetch the latest official upstream template to a temporary file first, and only continue if the fetch succeeds.
- Archive the current
SOUL.md, USER.md, and IDENTITY.md into .trash/ if they exist. - Write the fetched template to the workspace root as
BOOTSTRAP.md. - Tell the user to run
/new after completion so the next session starts from the restored bootstrap flow.
Use the bundled script:
CODEBLOCK0
Example:
CODEBLOCK1
Upstream source:
CODEBLOCK2
Constraints
- - Do not execute this skill without a second explicit confirmation in the current conversation.
- Do not hand-author a replacement bootstrap unless the user explicitly asks for a customized variant after syncing the official file.
- Only archive and remove
SOUL.md, USER.md, and IDENTITY.md from the workspace root; do not delete memory, project files, skills, or other workspace content. - Fetch the official template successfully before archiving or removing any existing identity files.
- Archive existing
SOUL.md, USER.md, and IDENTITY.md into .trash/ before removing them from the workspace root when those files exist. - Do not execute the bootstrap ritual automatically after syncing; stop after preparing the workspace and instruct the user to run
/new. - Mention that the official template is written for a fresh workspace and should be reviewed before reuse in an existing workspace.
Fallback
If the script cannot be used, run equivalent shell commands that (1) fetch the official BOOTSTRAP.md to a temporary file first, (2) archive existing SOUL.md, USER.md, and IDENTITY.md into .trash/ if present, (3) write the fetched template to the workspace root as BOOTSTRAP.md, and (4) avoid touching memory, project files, skills, or other workspace content.
Report back
Briefly report:
- - that the user gave the destructive confirmation
- whether
SOUL.md, USER.md, and IDENTITY.md were archived/cleared - that the latest official upstream template was fetched
- the destination path
- that the user should run
/new to trigger the re-bootstrap flow
ReSoul
重置工作区引导状态，以便下一个全新会话可以从官方上游的 BOOTSTRAP.md 开始。
主要工作流程
- 1. 警告运行 resoul 将获取官方的 BOOTSTRAP.md，然后将当前的 SOUL.md、USER.md 和 IDENTITY.md 归档到 .trash/ 中，如果它们存在于工作区根目录则将其移除。
- 在执行任何操作前要求明确的二次确认。不要将模糊的回复如ok或继续视为足够；需要用户明确同意将当前的 SOUL.md、USER.md 和 IDENTITY.md 从工作区根目录归档并移除。
- 首先将最新的官方上游模板获取到临时文件，仅在获取成功后才继续。
- 如果存在，将当前的 SOUL.md、USER.md 和 IDENTITY.md 归档到 .trash/ 中。
- 将获取的模板写入工作区根目录，命名为 BOOTSTRAP.md。
- 告知用户在完成后运行 /new，以便下一个会话从恢复的引导流程开始。
使用捆绑脚本：
bash
bash {{SKILLDIR}}/scripts/fetchofficial_bootstrap.sh
示例：
bash
bash {{SKILLDIR}}/scripts/fetchofficial_bootstrap.sh /root/.openclaw/workspace
上游来源：
bash
https://raw.githubusercontent.com/openclaw/openclaw/main/docs/reference/templates/BOOTSTRAP.md
约束条件
- - 在当前对话中未获得明确的二次确认前，不得执行此技能。
- 除非用户在同步官方文件后明确要求自定义变体，否则不得手动编写替代引导文件。
- 仅归档和移除工作区根目录中的 SOUL.md、USER.md 和 IDENTITY.md；不得删除记忆、项目文件、技能或其他工作区内容。
- 在归档或移除任何现有身份文件之前，必须成功获取官方模板。
- 在从工作区根目录移除现有 SOUL.md、USER.md 和 IDENTITY.md 之前，先将其归档到 .trash/ 中。
- 同步后不得自动执行引导仪式；在准备工作区后停止，并指示用户运行 /new。
- 提及官方模板是为全新工作区编写的，在现有工作区中重用前应进行审查。
备用方案
如果无法使用脚本，则执行等效的 shell 命令：(1) 首先将官方 BOOTSTRAP.md 获取到临时文件，(2) 如果存在，将现有的 SOUL.md、USER.md 和 IDENTITY.md 归档到 .trash/ 中，(3) 将获取的模板写入工作区根目录作为 BOOTSTRAP.md，(4) 避免触及记忆、项目文件、技能或其他工作区内容。
报告反馈
简要报告：
- - 用户已给出破坏性确认
- SOUL.md、USER.md 和 IDENTITY.md 是否已归档/清除
- 已获取最新的官方上游模板
- 目标路径
- 用户应运行 /new 以触发重新引导流程
