Daily development: local debugging, builds, and releases

This page explains how to have an Agent handle local debugging, production builds, preview verification, and pre-release checks. It isn't a script command list — state which page to verify, what artifact to build, and which entries or assets to sync, and the Agent reads the project scripts, picks the right commands, checks results, and reports risks.

Tasks to hand to the Agent

• Start the local dev server and get a reachable URL.
• Debug local startup, preview, or build failures.
• Run a production build and inspect the artifacts.
• Preview the build to confirm pages and data calls work.
• Run pre-release checks across menus, assets, SQL, BFF, and dataset calls.
• Sync platform menus, or update the live asset references a page uses.

Prerequisites

• The target project is open, and you've confirmed it's the app to debug or release.
• You know the page, route, or feature to verify.
• For builds: local code is saved and dependencies are installed.
• For releases: have the artifact URLs, page entry, or asset update requirements ready.

Common prompts

Start local debugging

请帮我启动当前项目的本地调试服务。
请先检查项目里有哪些可用脚本，再选择适合本地开发的启动方式。
启动后告诉我访问地址、是否有版本提示、是否有明显报错。

The AI may call: rabetbase run, rabetbase run start, rabetbase run dev.

Debug a failed local start

本地页面没有正常启动。请帮我排查原因。
重点检查 package 脚本、依赖安装状态、端口占用、CLI/SDK 版本提示和最近的错误日志。
请先给出原因判断，再告诉我修复步骤。

The AI may call: rabetbase run, rabetbase doctor, rabetbase run start, rabetbase run dev.

Run a production build

请帮我为当前项目做一次生产构建。
构建前先确认本地代码和数据接口配置是否完整。
构建后检查产物目录、JS/CSS 文件、资源路径和是否有构建错误。

The AI may call: rabetbase api pull, rabetbase run build.

Preview the build output

请帮我预览刚构建出来的产物。
请确认主要页面能打开，关键路由能访问，数据请求没有明显报错。
如果预览需要监听构建变化，也请说明会怎么处理。

The AI may call: rabetbase run preview.

Run pre-release checks

请帮我对这次改动做发布前检查。
请检查本地构建产物、页面路由、数据集调用、SQL/BFF 依赖、菜单入口和资源引用。
只列出通过项、风险项和阻断项，先不要执行发布或同步。

The AI may call: rabetbase run build, rabetbase dataset operations, rabetbase sql detail, rabetbase bff status, rabetbase menu sync.

Sync menus or update live assets

本次构建产物已经准备好。
页面入口是「<页面名称或路由>」。
资源地址是：
JS：<JS 资源地址>
CSS：<CSS 资源地址>
请帮我把页面入口和资源引用同步到平台。
执行前先预览会影响哪些菜单或资源；确认没有覆盖风险后再执行。

The AI may call: rabetbase menu sync, rabetbase menu update.

What to add to your prompt

• Page location: page name, route, component file, or menu entry.
• Debugging goal: start, troubleshoot, preview, build, or pre-release check.
• Build artifacts: output directory, JS/CSS URLs, or files to deliver.
• Release constraints: preview first, don't overwrite menus, don't touch unrelated files, don't sync immediately.
• Acceptance: which pages to open, which data to check, which interactions to confirm.

Completion checks

• The local service is reachable, or the failure cause is clearly identified.
• Build artifacts are generated, with JS/CSS and asset paths clear.
• The preview opens pages, and key data calls show no obvious errors.
• Pre-release risks, blockers, and items needing human confirmation are listed.
• Menu or asset syncs were previewed first, then executed per your confirmation.

Next step: if the release adds a new page entry, continue with "Code generation and menus". If the data structures behind the page are still unclear, go back to "APIs and datasets: pull config, see your data clearly".