OpenMetadata
Official@open-metadata · United States of America
A Single place to Discover, Collaborate, and Get your data right.
Agent Skills by OpenMetadata
Showing 23 vetted skills indexed across 1 GitHub repositories.
open-metadatasystematic-debugging
Diagnose failing tests, build errors, and runtime issues through a four-phase root cause analysis.
open-metadataconnector-standards
Load OpenMetadata connector development standards into context for building or reviewing connectors.
open-metadatascaffold-connector
Scaffold and implement new OpenMetadata connectors using schema-first code generation.
open-metadataui-core-components
Guides React/TSX layout code toward Box, Grid, Card, and Divider primitives with semantic color tokens.
open-metadatacode-review
Reviews code changes for spec compliance and code quality across branches, PRs, and staged diffs.
open-metadataplanning
Structures feature implementation through phased design, approval, and task planning before coding.
open-metadataplaywright-test
Generate Playwright E2E tests following OpenMetadata anti-flakiness patterns and lint rules.
open-metadatatest-enforcement
Validates test coverage for Java, Python, and React code changes against 90% coverage targets.
open-metadataconnector-audit
Audits OpenMetadata connectors through seven investigation prompts covering metadata, errors, auth, lineage, and scale.
open-metadatajava-checkstyle
Fixes Java formatting failures by running mvn spotless:apply and verifying the result.
open-metadataverification
Enforces running build, test, and lint commands as evidence before claiming task completion.
open-metadatadev-setup
Installs and verifies the OpenMetadata development toolchain on macOS and Linux.
open-metadatapr-checklist
Drafts and validates OpenMetadata pull request descriptions against the repository PR template.
open-metadataui-checkstyle
Runs ESLint, Prettier, and organize-imports on changed UI files to match CI checkstyle.
open-metadataconnector-review
Reviews OpenMetadata connector code against standards and posts scored findings to GitHub PRs.
open-metadatatdd
Guides RED-GREEN-REFACTOR test-driven development for Java, Python, and TypeScript codebases.
open-metadataopenmetadata-workflow
Routes development tasks to the correct OpenMetadata workflow skills at session start.
open-metadataweb-design-guidelines
Review UI code files against Vercel Web Interface Guidelines for accessibility and design compliance.
open-metadatavercel-composition-patterns
Guides React component refactoring using compound components, context providers, and composition patterns.
open-metadatavercel-react-best-practices
Applies React and Next.js performance optimization rules when writing, reviewing, or refactoring code.
open-metadataplaywright-validation
Validate branch UI changes with Playwright end-to-end tests.
open-metadatawriting-playwright-tests
Scaffold Playwright E2E tests using Page Object Model patterns and selectors.
open-metadataplaywright-test
Generate end-to-end Playwright tests following OpenMetadata patterns.
Frequently Asked Questions About OpenMetadata
FAQPage SchemaWhat specific tasks are enabled by these testing capabilities?▼
These capabilities enable the systematic validation of user interface changes through end-to-end testing. You can scaffold robust test suites using Page Object Model patterns, generate standardized verification routines, and perform regression checks on branch updates to ensure platform stability before merging code changes.
Which personas benefit from these testing patterns?▼
These patterns are designed for quality assurance engineers, frontend developers, and platform maintainers working within the OpenMetadata ecosystem. They are specifically intended for technical contributors responsible for maintaining UI consistency and verifying that new features or bug fixes do not disrupt existing platform functionality.
What are the prerequisites for implementing these test patterns?▼
Implementation requires an existing environment configured with Playwright and familiarity with the Page Object Model design pattern. Users must have access to the target repository to scaffold tests and should be prepared to define specific selectors that align with the existing interface structure of the platform.