Copy one Cloudflare D1 database into another of the same app's environments — refresh STAGING from prod, seed a PREVIEW from staging, or (guarded) push staging up to prod. Full mirror via scripts/db-clone.mjs. Use when asked to "clone a db", "refresh staging from prod", "copy prod data to staging", "seed a preview db", or to reconstitute a wiped staging DB. NOT for per-collection seeding (use the app's seedData/seed endpoints) or for schema migrations (use db-migrations).
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Wraps scripts/db-clone.mjs (pnpm db:clone): exports a source Cloudflare
D1 database and imports it into a target, making the target an exact mirror
(every target table dropped, then re-imported). Database names are discovered from
each app's wrangler.jsonc, so it works for any app + any pair of its environments.
node scripts/db-clone.mjs --app <app> --from <env> --to <env> [--dry-run] [--yes]
# or: pnpm db:clone --app <app> --from <env> --to <env>
<env> is prod (the wrangler.jsonc top level) or any key under env.*
(staging, preview, …).
Mobile / no-laptop: there's also a db-clone GitHub Action
(.github/workflows/db-clone.yml) — Actions → Run workflow → app/from/to from
the GitHub app. It reuses the repo's CLOUDFLARE_* secrets (no Cloudflare site
needed); a prod target requires the confirm_target_db input (passed as
--confirm), and the pre-clone backup is uploaded as an artifact. For
non-interactive runs the script takes --confirm <db> in place of the typed
prompt.
| Situation | Use |
|---|---|
| "Is the data still there?" / "how many rows / bookings / users" — check before cloning | pnpm db:counts --app <app> --env <env> (read-only) or the db-counts Action |
| "Make staging look exactly like prod" / "refresh staging" / "seed a preview from staging" | this skill |
| "Reconstitute the wiped staging DB" (and prod still has the data) | this skill (--from prod --to staging) |
| Load a specific org / CSV import into a fresh DB | the app's seedData/ + seed endpoints — NOT this |
| The source/target data is gone everywhere | re-seed from seedData/, don't clone |
| Add/alter a table (schema change) | the db-migrations skill |
A clone copies all data as-is; it is not a substitute for seeding curated fixtures or for migrations.
--dry-run first. Read back the resolved names (e.g.
velo-db → velo-staging-db) and the ordered plan before doing anything real.
The dry run needs no Cloudflare credentials.--from = the keeper, --to = the one wiped). Source == target is refused..db-backups/ first.
Don't pass --yes to a prod target unless the human explicitly asked for an
unattended run. The default direction is prod → staging, never the reverse.CLOUDFLARE_ACCOUNT_ID +
CLOUDFLARE_API_TOKEN (account → D1 Edit). Without them, only --dry-run
works. wrangler whoami should resolve before a real run.npx wrangler d1 execute <target> --remote --command "SELECT (SELECT COUNT(*) FROM user) users, (SELECT COUNT(*) FROM organization) orgs".--dry-run to confirm names + direction..db-backups/.See writeups/guides/db-clone-guide.md for the full reference.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Accessibility review for Vue surfaces — the code-cleaning analog of /code-review and /simplify, pointed at WCAG/ARIA. Reviews just your diff (or a package/file), rates findings by severity, and either comments inline on the PR (--comment) or applies the safe fixes for you (--fix). Steers the depth-aware `a11y` subagent. Use when asked to "check accessibility", "a11y this", "audit ARIA/keyboard", or run /a11y.
日本語の概要は準備中です。原文の説明を表示しています。
Emit a blocking question the owner can read in ~10 seconds and answer in one reply — the scannable, recommendation-first handoff every agent posts when it hits a fork it can't own. Leads with the one decision + a recommendation, carries the 🤖 provenance header, doubles as the
日本語の概要は準備中です。原文の説明を表示しています。
Audit packages for documentation completeness, detect drift between code and docs, and maintain documentation quality across the monorepo. Use when checking package docs, running audits, or reviewing documentation health.
日本語の概要は準備中です。原文の説明を表示しています。
Author a placeable layout block that looks right at ANY pane size. The one hard rule — size to the PANE with container queries (@container), never the viewport — plus list/form playbooks and the sizing contract (minWidth etc.) the viability metric reads. Use when adding/converting a croutonLayoutBlocks block, or when a block overflows/breaks in a narrow pane.
日本語の概要は準備中です。原文の説明を表示しています。
When a bug or regression is reported, the FIRST step — before fixing — is to research how and when it was introduced (git archaeology), then record that finding on the tracking issue/PR. Use the moment a bug, error, broken build, or "this used to work" is reported, before writing a fix. Produces a first-bad-commit (or "not a code regression") note you paste onto the issue.
日本語の概要は準備中です。原文の説明を表示しています。
Smart, granular git commits following monorepo conventions. Analyzes changes, filters to session-relevant files, groups by intent, and uses conventional commit format. Use when committing code changes.
日本語の概要は準備中です。原文の説明を表示しています。