// Use when the user asks to deploy, ship, release, or push OntoBricks to Databricks. Wraps the Databricks Asset Bundle deploy for the FastAPI app and the MCP server, with the bootstrap-perms safety net described in README.md.
| name | deploy |
| description | Use when the user asks to deploy, ship, release, or push OntoBricks to Databricks. Wraps the Databricks Asset Bundle deploy for the FastAPI app and the MCP server, with the bootstrap-perms safety net described in README.md. |
The canonical deploy steps are in README.md §Deploying / Installing and
.cursorrules §"When asking to deploy". The Make targets live in
Makefile. This skill only sequences pre-flight and post-deploy checks.
databricks --version — CLI present.databricks auth describe — authenticated against the right workspace. If not, use the databricks-authentication skill.git status — clean tree (or user has acknowledged uncommitted changes).uv run pytest -q — tests pass. Do not deploy on red.| Command | When |
|---|---|
make deploy | dev — deploy + start FastAPI app |
make deploy-all | dev — deploy + start both apps (FastAPI + MCP) |
make deploy-mcp | only MCP server changed |
make deploy-prod | production target |
make deploy-no-run | deploy artifacts without starting apps |
make bundle-validate | validate databricks.yml only |
make bundle-summary | preview what will deploy |
make deploy runs scripts/bootstrap-app-permissions.sh automatically on
the first deploy (see README.md). If the user runs databricks bundle deploy directly, run make bootstrap-perms once afterwards (idempotent).
sql-warehouse and volume are bound. If missing, the user must bind them manually (binding cannot be done via DAB)./healthz to confirm the FastAPI app is responsive.When the user says "release vX.Y.Z" rather than just "deploy":
make testpyproject.tomlgit add -A && git commit -m "Release vX.Y.Z" && git tag vX.Y.Z && git push origin main --tagsmake deploy (or make deploy-prod)changelog skill).databricks bundle deploy directly without remembering make bootstrap-perms for first-time deploys.deploy-no-run).Use when adding a new subpackage under back/core/, back/objects/, or agents/ — e.g. a new graph DB engine, W3C parser, industry importer, reasoning module, or domain class. Enforces the checklist defined in .cursor/07-project-conventions.mdc.
Use after any code change (feature, fix, refactor, review fixup) to update /changelogs/YYYY-MM-DD.log and run the test suite. Mandatory post-change routine — see .cursorrules.
Use when the user asks for a code review, asks to "review the code", or requests review of a feature/PR/branch. Runs the OntoBricks review checklist defined in .cursorrules.
Use when the user asks to "refactor", restructure, clean up, simplify, deduplicate, extract, or reorganize code. Enforces the Martin Fowler discipline defined in src/.coding_rules.md and .cursor/08-testing-and-deployment.mdc.