All authors

Claude Skills by datacontract
github.com/datacontract8 skills0 installs1 views
- Breaking Change CheckData Product Owners and Builders. Compares two versions of an ODCS data contract (a working copy against git HEAD, a branch, a pull request, or two files or URLs) with `datacontract changelog` and `datacontract breaking`, adds the semantic changes no tool detects, and returns a verdict (breaking, needs review, safe), the version bump, a changelog entry, and a migration note for consumers. Use when the user changes a data contract and asks whether the change is breaking or backward compatible,...Votes: 0GitHub stars: 4
- Contract CiData Product Builders and Platform Engineers. Sets up continuous data contract checks with the Data Contract CLI in GitHub Actions, GitLab CI, Azure DevOps, Airflow, or plain cron: lint and breaking-change checks on every pull request, data tests after every load and on a schedule, credentials from the CI secret store, and optional publishing of results to Entropy Data. Use when the user wants to run data contract tests in CI/CD, on a schedule, in a pipeline or orchestrator, block breaking co...Votes: 0GitHub stars: 4
- Create Data ContractData Product Builders and Owners. Creates a new data contract in the Open Data Contract Standard (ODCS), either data-first by importing it from an existing table, SQL DDL, dbt manifest, Avro, JSON Schema, or Excel template with the Data Contract CLI, or contract-first from requirements described in plain language, then fills in descriptions, semantics, keys, servers, team, and terms, and lints it until it is valid. Use when the user wants to create, write, draft, scaffold, or generate a data ...Votes: 0GitHub stars: 4
- Datacontract CliCore. Install, upgrade, and configure the Data Contract CLI (`datacontract`), the open-source tool every other data contract skill builds on, and look up its documentation. Use when the user wants to install the CLI, pick the right extras for a data source, set up credentials for a server, check the CLI version, or when another skill's Step 0 says to verify the CLI.Votes: 0GitHub stars: 4
- Datacontract EditorOpens a data contract in the Data Contract Editor, the visual web editor for ODCS with a diagram, form, and YAML view, live HTML preview, validation, and a test runner: locally against a file with `datacontract edit` or `npx datacontract-editor`, in Docker, or at editor.datacontract.com, plus share links and organization-specific customization (`customization.yaml`). Use when the user wants to view, edit, review, or present a data contract visually, open the editor, share a contract with a bu...Votes: 0GitHub stars: 4
- Export Data ContractData Product Builders. Generates code and artifacts from an ODCS data contract with the Data Contract CLI: SQL DDL, dbt models, sources, staging SQL and tests (`datacontract dbt sync`), Avro, JSON Schema, Protobuf, Pydantic, SQLAlchemy, Spark, Iceberg, BigQuery schemas, Great Expectations, SodaCL, DQX, HTML, Markdown, Mermaid, Excel, and an HTML catalog of many contracts, then wires the output into the user's project. Use when the user wants to implement a data product from a contract, create...Votes: 0GitHub stars: 4
- Quality RulesData Product Builders and Owners. Proposes and adds data quality rules and service levels to an ODCS data contract: schema constraints, library metrics (rowCount, nullValues, missingValues, invalidValues, duplicateValues), SQL rules, freshness and retention, each with a dimension, id, and tags, grounded in the field semantics and, if the user agrees, in a profile of the actual data, then lints and test-runs them. Use when the user wants to add quality checks, data quality expectations, SLAs, ...Votes: 0GitHub stars: 4
- Test Data ContractData Product Builders and Owners. Runs `datacontract test` against the data source in a contract's servers block (Snowflake, Databricks, BigQuery, Postgres, S3, Kafka, local files, and more), sets up the connection and credentials, and when checks fail, investigates each failure and says whether the data, the contract, or the connection is wrong, with a concrete fix. Use when the user wants to test, validate, or check data against a data contract, asks why a contract test fails, gets a schema...Votes: 0GitHub stars: 4