// Meta-skill loaded at session start. Directs Claude to check for applicable OpenMetadata skills before starting any task. Ensures structured workflows are followed.
Deep reliability audit for OpenMetadata connectors — runs 7 investigation prompts (metadata, errors, auth, lineage, scale, synthesis, implementation) against connector standards
Use to review code changes with a two-stage process - first checking spec/requirements compliance, then code quality. Works on staged changes, branches, or PRs.
Use when starting a non-trivial feature, refactor, or multi-file change. Forces structured design thinking before writing any code - brainstorm approaches, get approval, then create a step-by-step implementation plan.
Use when implementing new features or fixing bugs to enforce test-driven development. Guides the RED-GREEN-REFACTOR cycle for Java (JUnit), Python (pytest), and TypeScript (Jest/Playwright) in OpenMetadata.
Use before claiming any task is complete. Requires running actual verification commands and showing evidence — no "should work" claims without proof.
Build a new OpenMetadata connector from scratch — scaffold JSON Schema, Python boilerplate, and AI context using schema-first architecture with code generation across Python, Java, TypeScript, and auto-rendered UI forms.
| name | openmetadata-workflow |
| description | Meta-skill loaded at session start. Directs Claude to check for applicable OpenMetadata skills before starting any task. Ensures structured workflows are followed. |
This skill is loaded automatically at session start. It ensures you follow the right workflow for every task.
Check which skills apply to your task and use them. This is not optional — if a skill applies, you must follow it.
| Task type | Required skill(s) |
|---|---|
| New feature (multi-file) | /planning then /tdd then /test-enforcement then /verification |
| Bug fix | /systematic-debugging then /tdd (write regression test) then /verification |
| New API endpoint | /planning then /tdd then /test-enforcement (must include integration test) |
| New connector | /connector-standards then /connector-building then /test-enforcement |
| UI component | /tdd then /test-enforcement (must include Jest + Playwright if user-facing) |
| Code review / PR review | /code-review then /test-enforcement |
| Connector review | /connector-review |
| E2E test creation | /playwright |
| Finishing implementation | /test-enforcement then /verification |
Note: Connector skills (
/connector-standards,/connector-building,/connector-review) and/playwrightare part of the OpenMetadata Skills plugin and ship together with this workflow skill. They are defined in theskills/directory alongside this file.
Plan before coding. For any non-trivial task, use /planning to design the approach before writing code.
Test-first when possible. Use /tdd to write failing tests before implementation. This applies to Java, Python, and TypeScript equally.
Always enforce test coverage. Before any PR, use /test-enforcement to verify:
Verify with evidence. Use /verification before claiming completion. Show actual test output, not claims.
Review before merging. Use /code-review for two-stage review (spec compliance + code quality).
When your task touches multiple layers, ensure all are synchronized:
openmetadata-spec/ → run make generateyarn parse-schemabootstrap/sql/migrations/locale/languages/en-us.json then run yarn i18nmvn spotless:applymake py_format && make lintyarn organize-imports:cli && yarn lint:fix && yarn pretty:base --writeyarn license-header-fix)yarn generate:app-docsIf CLAUDE.md instructions conflict with any skill, CLAUDE.md wins. Skills are supplementary workflows, not overrides.