fabricks-devops-issues-resolver
Fabricks DevOps Issues Resolver
Picks up where fabricks-devops-issues's diagnose <id> leaves off (a local,
uncommitted file fix) and carries it through to a verified, closed ticket.
Read that skill first if you haven't already — this one assumes its
list/diagnose output and reuses its file-resolution logic.
This skill has real side effects fabricks-devops-issues doesn't: it commits
and pushes to the user's own branch, runs real Databricks jobs, and can close
real tickets. Treat every write (push, job run, ticket close) as something to
narrate plainly, not do quietly — the user should never be surprised by what
happened when they read back the conversation.
You'll need <repo_root> (the Fabricks.Runtime checkout) and the user's own
dev branch name (e.g. dev_dominik) — ask if not already clear from context.