菜单
Use at the start of a session in a cleanvibe-scaffolded project, at most weekly — fetch cleanvibe's updates page and refresh this repo's .claude/skills/ to the latest shipped versions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cleanvibe-update-check |
| description | Use at the start of a session in a cleanvibe-scaffolded project, at most weekly — fetch cleanvibe's updates page and refresh this repo's .claude/skills/ to the latest shipped versions. |
This repo's .claude/skills/ were vendored by cleanvibe. cleanvibe ships new and revised skills over time — when one lands, every cleanvibe-scaffolded project should pick it up.
The check is weekly, not per-session. At the top of a session, look at the last cleanvibe update check date recorded in this repo's CLAUDE.md ## Skills section. If it has been more than 7 days:
WebFetch https://cleanvibe.emmaleonhart.com/updates.md. This is the canonical, hand-maintained page describing every skill cleanvibe ships, keyed by the cleanvibe version that introduced or revised it..claude/skills/. If the page lists newer skills or revisions, update the corresponding .claude/skills/<slug>/SKILL.md files to match. Match the wording from updates.md; don't paraphrase.## Skills section. Commit with a message describing which skills were refreshed.If the fetch fails (offline, DNS, page not yet up), leave the date alone and try next session — the check is opportunistic, not mandatory.
Use when starting any session of relatively extensive or large-scale autonomous work — above all any large-scale population of queue.md with created tasks — to run the three local-cron productivity playbook (work-loop, auto-flush, status-report).
Replicate the methods of "Neural Computers" (arXiv:2604.06425) and produce a runnable artifact, a published findings report, and a downloadable replication package.
Reproduce results from the Sutra paper — build the compiler, run the 10-program smoke test, run the rotation-vs-Hadamard capacity tables (LLM + ESM-2 protein-LM substrates), the chained-bind crosstalk experiment, plus the loop function decl + codebook test suites.
Use when the user says "cron job", "cron", or asks to "schedule" a task — they mean the in-session CronCreate tool firing locally on their own running computer, with standing consent; just set it up.
Use when the user sends a continuous series of "stop" messages (e.g. "stop stop stop") or otherwise very explicitly demands an immediate halt — kill all running processes, background jobs, and GitHub Actions runs for this repo, then take no further actions.
Use when doing any multi-step or planning work in a cleanvibe-scaffolded project — enforces plan-into-queue.md-first, the todo.md→queue.md→devlog.md flow, delete-don't-check completion, task-tool mirroring, and tests/CI discipline.