Skip to content

Minor improvements to databricks-serverless-migration Skill #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
alexnastetsky wants to merge 2 commits into
base: main
Choose a base branch
from
+19 −0
Open

Minor improvements to databricks-serverless-migration Skill #124

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a7424c4
always generate migration report. use subagents with multiple workloads.
alexnastetsky Jun 2, 2026
41c551c
adding list of questions to the user
alexnastetsky Jun 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions skills/databricks-serverless-migration/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,17 @@ Analyze existing Databricks code for serverless compute compatibility and guide
- Troubleshooting serverless-specific errors after migration
- Choosing between Performance-Optimized and Standard mode

## Input to get from the user
Ask the user for explicit input parameters for the following items, providing reasonable defaults:
- Which workspace contains the source workloads?
- Which workspace will contain the migrated workloads?
- What is the catalog and schema where output from the test migrated jobs should go?
- How should the test jobs be prefixed or tagged?
- Where in the workspace should the converted code go?
- What compute should be used for reading output produced by classic jobs for comparison (if serverless is not available)?

Prior to presenting these questions, make sure there are 6 questions (so you don't miss any of the above).

## Understanding Migration Blockers

Migration blockers fall into three categories. Focus your effort on category 2 — that's where this skill helps most.
Expand Down Expand Up @@ -623,6 +634,14 @@ Submission is optional and opt-in. We use reports to prioritize new patterns and

**Never transmit the report automatically.** The user owns their data and must review before sharing.

## Success report

If the migration was successful, generate a report as well, using similar methods. For each workload migrated, show what was done.

## Multiple workload migration

When migrating multiple workloads in one session, parallelize this work as much as possible to migrate multiple workloads in parallel, including using subagents.

## Reference Guides

For detailed workarounds and code examples beyond the quick fixes above:
Expand Down