تشغيل أي مهارة في Manus بنقرة واحدة

check-updates

النجوم٥

التفرعات٠

آخر تحديث٢٣ يونيو ٢٠٢٦ في ٢٣:٣٣

Check the CURRENT Convex app's pinned components against the latest recommended versions and offer to upgrade them — e.g. the passkey auth component's new email-first sign-in. TRIGGER when the user runs /check-updates or $check-updates, asks 'are my components up to date', 'any updates', 'upgrade auth', 'upgrade my components', or wants the newest features after a quickstart. Applies each upgrade behind a build gate (verify-or-revert) with the user's consent.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

get-convex

get-convex/convex-codex-plugin

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	check-updates
description	Check the CURRENT Convex app's pinned components against the latest recommended versions and offer to upgrade them — e.g. the passkey auth component's new email-first sign-in. TRIGGER when the user runs /check-updates or $check-updates, asks 'are my components up to date', 'any updates', 'upgrade auth', 'upgrade my components', or wants the newest features after a quickstart. Applies each upgrade behind a build gate (verify-or-revert) with the user's consent.
license	Apache-2.0

Check + apply component updates

Run from the app's project root (where package.json lives — the convex-app/ subdir for a quickstart). Detect stale components against the anteater registry:

curl -fsSL https://basic-anteater-667.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjs

COMPONENTS_UP_TO_DATE → tell the user everything's current. Done.
COMPONENTS_STALE=<n> + a JSON array → for each entry, summarize for the user: the component, installed → current, the summary (what's new), and whether it's breaking. Then ASK before changing anything — "Upgrade <name> to get
? [y/n]". Never upgrade without an explicit yes.

On a yes, apply that entry's migration:

Install the new ref (migration.install) with the project's package manager.
Apply migration.steps in order — the call-site changes. Read the existing code first; make the minimal change each step describes. Delegate any convex/ edits to the convex-expert skill/subagent.
GATE — verify or revert. Run every command in migration.gate (e.g. pnpm exec tsc --noEmit, pnpm exec next build). If ANY fails, revert (git checkout -- ., or reinstall the old ref) and tell the user it didn't apply cleanly — never leave the app half-migrated.
Smoke — give the user the migration.smoke check to run (the runtime behavior the build gate can't prove), e.g. register → sign out → sign in by the same email.

Rules:

breaking: true needs extra care: confirm explicitly, snapshot first (commit/branch), and if the steps aren't mechanical, ask the user rather than guessing.
Don't auto-publish. If the app is already live on *.convex.app / a custom domain, the upgrade only reaches the live site on re-publish — confirm before re-deploying (no surprise downtime on a live domain).
One component at a time; gate each before the next.

المزيد من هذا المستودع

نفس المستودع

workflow

get-convex/convex-codex-plugin

Build a durable multi-step pipeline on Convex where each step runs in order and is retried independently on failure (transcribe→summarize→email, ETL, order fulfillment, any 'do A then B then C, retry each' job). Use @convex-dev/workflow — do NOT hand-roll a chain of scheduler calls or a custom jobs table. TRIGGER on multi-step / pipeline / 'retry each step' / long-running orchestration requests.

2026-07-225

improve-convex-plugin

get-convex/convex-codex-plugin

Send THIS Codex session's transcript to the Convex quickstart backend for an AI post-mortem that improves the whole system (runbook, bootstrap, skills). TRIGGER when the user runs $improve-convex-plugin, or after a quickstart build says 'send feedback', 'report how that went', or 'help improve the quickstart'.

2026-07-165

labs-quickstart

get-convex/convex-codex-plugin

LABS — the FULL Convex quickstart experience: scaffold a running Next.js + shadcn app from one sentence with passkey (WebAuthn) sign-in and a live in-app Chef feedback panel pre-baked, build the idea live, then PUBLISH it to a public https://<app>.convex.app URL (with the user's confirmation before publishing). TRIGGER when the user runs $labs-quickstart, or asks for the full/labs quickstart, a published/public app, sign-in/passkeys, or the in-app feedback panel from scratch. For a plain local-only scaffold use $quickstart instead. SKIP when there's already a Convex project in the cwd.

2026-07-165

quickstart-improve

get-convex/convex-codex-plugin

Backward-compatible alias for improve-convex-plugin. Send THIS Codex session's transcript to the Convex quickstart backend for an AI post-mortem that improves the whole system. TRIGGER when the user runs $quickstart-improve (the former name of $improve-convex-plugin).

2026-07-165

quickstart

get-convex/convex-codex-plugin

Scaffold a running Next.js + shadcn Convex app from one sentence — convex dev + next dev already running — then build the idea live (runs locally). TRIGGER when the user wants to START a new Convex app from scratch — e.g. they ran $quickstart, said 'scaffold a new app', 'build me an app where users can ___', or 'new app'. SKIP when there's already a Convex project in the cwd.

2026-07-165

auth

get-convex/convex-codex-plugin

Add sign-in (passkeys by default, OAuth/password optional) to the current Convex app, wired correctly incl. auth.config.ts. TRIGGER on a login/auth request for an existing app.

2026-07-155

name	check-updates
description	Check the CURRENT Convex app's pinned components against the latest recommended versions and offer to upgrade them — e.g. the passkey auth component's new email-first sign-in. TRIGGER when the user runs /check-updates or $check-updates, asks 'are my components up to date', 'any updates', 'upgrade auth', 'upgrade my components', or wants the newest features after a quickstart. Applies each upgrade behind a build gate (verify-or-revert) with the user's consent.
license	Apache-2.0

Check + apply component updates

Run from the app's project root (where package.json lives — the convex-app/ subdir for a quickstart). Detect stale components against the anteater registry:

curl -fsSL https://basic-anteater-667.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjs

COMPONENTS_UP_TO_DATE → tell the user everything's current. Done.
COMPONENTS_STALE=<n> + a JSON array → for each entry, summarize for the user: the component, installed → current, the summary (what's new), and whether it's breaking. Then ASK before changing anything — "Upgrade <name> to get
? [y/n]". Never upgrade without an explicit yes.

On a yes, apply that entry's migration:

Install the new ref (migration.install) with the project's package manager.
Apply migration.steps in order — the call-site changes. Read the existing code first; make the minimal change each step describes. Delegate any convex/ edits to the convex-expert skill/subagent.
GATE — verify or revert. Run every command in migration.gate (e.g. pnpm exec tsc --noEmit, pnpm exec next build). If ANY fails, revert (git checkout -- ., or reinstall the old ref) and tell the user it didn't apply cleanly — never leave the app half-migrated.
Smoke — give the user the migration.smoke check to run (the runtime behavior the build gate can't prove), e.g. register → sign out → sign in by the same email.

Rules:

breaking: true needs extra care: confirm explicitly, snapshot first (commit/branch), and if the steps aren't mechanical, ask the user rather than guessing.
Don't auto-publish. If the app is already live on *.convex.app / a custom domain, the upgrade only reaches the live site on re-publish — confirm before re-deploying (no surprise downtime on a live domain).
One component at a time; gate each before the next.