HELP: "Usage: npx @crowandraven/evalkeeper <command> [options]\n\nCommands:\n add pages Write Evalkeeper's pages and their glue into your Next.js app\n migration Bring your copy of Evalkeeper's tables up to this version\n\nadd pages copies Evalkeeper's eval pages, components, and their glue into your\nNext.js app, fitted to its folders and import alias.\n\nOptions:\n --base <path> Where the pages live in your app (default: evals)\n --alias <name> Your import alias, e.g. \"@\" or \"~\" (default: from tsconfig.json)\n --root <dir> Where the alias points, e.g. \"src\" (default: from tsconfig.json)\n --no-cron Leave out the weekly check's cron route\n --only <names> Copy only these, comma-separated: pages (hub, suite, run,\n rate, compare, side-by-side, feedback, cron), components\n and glue by name (AnswerKey, actions, …), the groups\n \"pages\" and \"components\", or \"index\" for a starter\n lib/evalkeeper/index.ts\n --force Overwrite files that already exist (never your lib/evalkeeper/index.ts)\n --dry-run Show what would be written, and write nothing\n --help Show this\n\nmigration writes Evalkeeper's models to evalkeeper.prisma beside your\nPrisma schema (moving any you pasted into your own schema there), and\nthe SQL that brings your tables up to this version, from the schema\nfiles through your own `prisma migrate diff`. It never reads or\nwrites a database. Without --write it only shows what it would do.\n\nOptions:\n --write Write the schema files (and the SQL, to --out)\n --out <file> Where the SQL goes; needed with --write when there is SQL\n --schema <path> Your Prisma schema file or folder (default: from your config)\n --accept-drops Allow a change that drops columns or tables, with their data\n" = ...
The command's help text.