Agent Skills
› openclaw/clawhub
› convex-check-updates
convex-check-updates
GitHub检测并升级 Convex 组件，经用户确认后逐个执行迁移、构建门禁及冒烟测试，失败自动回滚。
Trigger Scenarios
需要检查或升级项目依赖版本时
执行带有构建门禁的自动化部署流程时
Install
npx skills add openclaw/clawhub --skill convex-check-updates -g -y
SKILL.md
Frontmatter
{
"name": "convex-check-updates",
"description": "Check the current app's pinned Convex components against recommended versions and upgrade them behind a build gate."
}
check-updates
Detect stale Convex components in the current app against the anteater registry and, with explicit user consent, upgrade them one at a time behind a build gate (typecheck + next build). Each upgrade is gated and smoke-tested before the next.
Workflow
- Run
curl -fsSL https://graceful-tiger-715.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjsfrom the project root. - If COMPONENTS_UP_TO_DATE: tell the user; done.
- If COMPONENTS_STALE=
: list each stale entry (component name, installed → current, summary, breaking flag) and ask the user before touching anything. - On yes: install the new ref, apply each migration.steps change (delegate convex/ edits to convex-expert), run every migration.gate command.
- If any gate command fails: revert (git checkout -- . or reinstall old ref) and report; never leave the app half-migrated.
- Give the user the smoke check (migration.smoke) to run after each successful upgrade.
- Repeat for each stale component, one at a time.
Rules
- Never upgrade without an explicit user yes — not even a minor version.
- Gate each component individually before moving to the next.
- breaking:true upgrades require a snapshot (commit or branch) before applying.
- Do not auto-republish a live *.convex.app site after upgrading without user confirmation.
Version History
- d6a8c68 Current 2026-08-20 02:43
