sealos-databaselisted

# Sealos Database Use this skill to give a project a real Sealos Cloud database during development. The default outcome is: identify the app's database need, create or reuse a Sealos database with `sealos-cli`, fetch connection details, wire only the needed local env vars, and verify the app can connect. ## Safety Rules 1. Never print database passwords or full connection strings in the final answer. 2. Do not overwrite an existing env value without confirming or preserving the old value. 3. Do not commit `.env`, `.env.local`, connection strings, passwords, kubeconfig, or Sealos auth files. 4. Ask before enabling public database access. Prefer private connections when the app runs inside Sealos/Devbox. 5. Ask before destructive operations: `database delete`, `backup-delete`, restoring over a name that may collide, or disabling access that an active app depends on. 6. Use JSON output from `sealos-cli` by default and parse it instead of scraping table output. ## Workflow ### 1. Resolve the target project Confirm the working directory with `pwd` or `git rev-parse --show-toplevel`. Run the analyzer when a project directory is available: ```bash node <SKILL_DIR>/scripts/analyze-project-database.mjs <project-dir> ``` Use the analyzer result as a starting point, then inspect the real files it cites before editing anything. It intentionally avoids printing secret values. ### 2. Check `sealos-cli` Prefer an existing `sealos-cli` binary: ```bash sealos-cli --version sealos-