Check for updates and upgrade Ouroboros to the latest version
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Upgrade Ouroboros without changing the installation's manager, environment, or optional-dependency profile.
ooo update
/ouroboros:update
The native command is the single source of truth. Run it with the active runtime's run_shell capability.
Run ouroboros update --check.
ask_user capability) to choose Update now or Skip. On Update now, run ouroboros update --yes. When the user actively uses both Claude Code and Codex, run ouroboros update --yes --runtime all instead; it refreshes both host integrations without changing the configured execution backend. Show the command's result.If the check fails but ouroboros update --help works, report the native error and stop. Never substitute a manual upgrade, and never infer ownership from uv tool list, pipx list, PATH order, directory names, or the active agent runtime.
If ouroboros update --help does not work, this is a legacy install that predates the receipt-bound updater. Fail closed: only a read-only ouroboros --version is allowed. Explain that the original manager, environment, and extras cannot be proven, and ask the user to rerun their exact original install command (including its ouroboros-ai[...] extras and custom manager root), or to do a fresh isolated install if they do not know it. Run no package upgrade, plugin refresh, or setup command on this path.
After a successful update, relay the command's restart guidance (Claude may use /reload-plugins or restart; active Codex sessions need a restart). If project instruction content needs regeneration, suggest ooo setup; never edit project instruction files as part of the update.
The updater replays the environment's install receipt, so the Claude SDK and MCP 2 profiles are never combined or substituted. Other options: --dry-run, --prerelease; see ouroboros update --help.
End the final response with exactly one line ◆ <current state> → next: <recommended action>. Derive the state from live session state via ouroboros_session_status when available, otherwise from this skill's actual outcome. Never use a linear Step N of M footer; when the next step is a real choice, list 2-3 options.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use when the work spans several files or replaces a framework, language, auth, storage, or API layer (rewrites and migrations included), and the user wants it to end up working and tested. Asks only what is missing, writes a spec with acceptance criteria, then runs and verifies it in the background. Not for questions, small edits, or an existing Seed (use run).
中文简介正在准备中。当前显示原文说明。
Scan and manage brownfield repository/worktree defaults for interviews
中文简介正在准备中。当前显示原文说明。
Cancel stuck or orphaned executions
中文简介正在准备中。当前显示原文说明。
Use when the user wants proof that finished work meets its acceptance criteria, not just that tests pass: 'verify it is actually done', 'check it against the spec', 'evaluate the run'. Runs mechanical checks, a semantic review per criterion, and multi-model consensus when uncertain. With execution.auto_evolve on (the default), a rejected result with a Seed continues into a Ralph fix loop; pass auto_evolve: false to verify only.
中文简介正在准备中。当前显示原文说明。
Start or monitor an evolutionary development loop
中文简介正在准备中。当前显示原文说明。
Use when the user wants to build or change something but the request is vague or open-ended: 'help me figure out what to build', 'I'm not sure what it should do', 'add X' with no details, or no clear definition of done. Runs a short Socratic interview that turns the idea into goals, constraints, and acceptance criteria before any code is written. Not for simple questions, small clear edits, or an existing Seed.
中文简介正在准备中。当前显示原文说明。