DBHub Database Workflow

This is a company internal DBHub skill, not an official Bytebase skill. DBHub itself is provided by @bytebase/dbhub; this skill defines the company workflow around it.

Use DBHub MCP as the only database access path. Do not write ad hoc database connection scripts unless the user explicitly asks for a custom tool.

If DBHub MCP tools are unavailable, stop database work. Do not fall back to direct SQL Server connections, application connection strings, sqlcmd, ADO.NET, PowerShell SQL modules, or custom scripts as a substitute for DBHub.

Hard Stop Conditions

Stop the current task and ask the user to restart the agent session when any of these happen:

• You installed DBHub MCP in this session.
• DBHub MCP configuration was written, but DBHub tools are still not listed in the current session.

After a hard stop, do not try to query the database in the same session. Do not try to use the DBHub CLI to pass SQL on the command line. DBHub CLI starts an MCP server; SQL must be executed through MCP tools after the agent session restarts and the tools are loaded.

Changing dbhub.toml or .env after DBHub MCP is already loaded is not a hard stop. The DBHub proxy reloads project configuration on the next dbhub_status, execute_sql, search_objects, or dbhub_custom_tool call.