data-engineering

Plugin data-engineering from marketplace data-with-baraa in DataWithBaraa/claude-code-data-engineering-skills. Commands read from the repo's manifest — 6 days ago.

Skills (16)

• big-review

  Use once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs and the repo, and propose improvements with effort and risk.

• contract

  Use when a new source is connected or a source changes how it delivers, to write the data contract with the source system, the format, the schema, the quality rules, the delivery, the owner and the change process.

• cost-review

  Use for the monthly cost review of the platform, to see where the compute and the storage money goes, per job, pipeline and table, and what to cut.

• data-product

  Use when a table is served to consumers, released or changed, to build everything a consumer needs as a data product, the guide, the data model, the metrics, the starter queries, the quality, the releases and the data contract.

• docs

  Use after a change or a release, to write and refresh the runbook and the how-to guides of the project, so the runbook and the guides match the code.

• impact

  Use before you change a table, a column or a function, to see what it is built from, what depends on it, who reads it, which checks cover it, and the safe order of the change.

• incident

  Use when a job run failed with an error, to walk the incident from the error to the root cause, the workaround, two solutions, the future risks, the email drafts and the log entry.

• knowledge-refresh

  Use after a release, to compare the knowledge Claude Code reads, CLAUDE.md, the standards, the source pages and the incident log, with the code and the data, and propose what is stale, missing or wrong.

• metadata

  Use when the metadata of a source has to be built or extended, to describe every table and column, the names and types from the data with a script, the descriptions from the documents, never guessed.

• migration

  Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the migration plan with scenarios, acceptance numbers, the parallel run and the rollback.

• pr-review

  Use before a pull request or another change goes in, on a file, the current diff or a branch, to review it pass by pass against the project's own standards, with pushback.

• profile

  Use when a new source or new files arrive, to profile them before any data contract or pipeline code is written, the file formats, the schema, the data quality, the bad records, the relationships, the gaps and the personal data.

• quality

  Use to see which checks failed or warned, what was quarantined, how fresh the tables are, and whether each table is safe to use today.

• reconcile

  Use when two numbers that should agree do not, a report against its source, a rollup against its detail, two systems for the same table, to find where they diverge and why.

• test-data

  Use when a new function or a new table needs tests, to write test data with the edge cases and the expected result written first, never from production data.

• toolkit

  Use to build or rebuild the documentation site of the project from the repo, the architecture, the data lineage, the call graph, the data model, the data quality, the runs and the data catalog.

Similar plugins