datahub-test-taxonomy
Skill13k starsChanged 3 months agoApache-2.0View on GitHub
Maintain the smart-testing test taxonomy: tag new or changed tests and drop deleted ones, tag any tests that have no tags yet, regenerate all test tags (optionally for one framework), or regenerate the taxonomy from the rubric. Use after adding, modifying, or deleting smoke-test pytest, Playwright, or metadata-ingestion tests, or when the taxonomy needs a refresh.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about datahub-project/datahub
- Kentra“Flink 2.0 + OpenLineage + DataHub = Lineage Graph”YouTube · Jun 25, 2025 · 545 views
- Jishanahmed AR Shaikh“Breakdown: Shipped It? Now Understand It. (Built Hands-Free with Wispr Flow)”YouTube · Oct 25, 2026 · 274 views
- Gourcer“datahub-project/datahub - Gource visualisation”YouTube · Sep 28, 2023 · 62 views
- edycutjong“Antigen — a prompt-injection immune system for DataHub”YouTube · Aug 10, 2026 · 39 views
- Ritesh“Blast Radius — DataHub Agent Hackathon”YouTube · Aug 9, 2026 · 20 views
The biggest 5 of 64 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 64
Talked about on GitHub, YouTube, Hacker News, Bluesky and Stack Overflow (64 times).
On GitHub · 50
- Feb 7, 2023[Feature] - DataHub on EKS (open source data catalog) — awslabs/data-on-eks6 reactions · 6 comments
- Aug 26, 2025Missing configuration for Kafka SSL and datahub-actions — acryldata/datahub-helm3 reactions · 3 comments
- Sep 22, 2026feat(warehouse-sources): add datahub run, assertion and profile tables — PostHog/posthog1 reaction · 6 comments
- Apr 10, 2026RFC for MCP server improvements (FastMCP v3, Code Mode, OIDC OBO) — acryldata/mcp-server-datahub1 reaction · 1 comment
- Dec 12, 2025[Feature]: super coarse memory usage regression test — BrokkAi/brokk-app1 reaction · 4 comments
45 more on GitHub
- Sep 11, 2025feat: Add custom labels support for all Job and CronJob resources — acryldata/datahub-helm1 reaction · 8 comments
- Jun 18, 2023Error when generating Python client for DataHub graphql files — mirumee/ariadne-codegen1 reaction · 2 comments
- May 31, 2023Quiet mode for dags list-import-errors — apache/airflow1 reaction · 13 comments
- Apr 28, 2023Integrate with Linkedin's Datahub project — StarRocks/starrocks1 reaction · 2 comments
- Nov 9, 2026chore(deps): bump acryl-datahub from 1.7.0.17 to 1.7.0.19 — acryldata/mcp-server-datahub0 reactions
- Nov 9, 2026chore(deps-dev): bump acryl-datahub from 1.7.0.18 to 1.7.0.19 in the python-dev-dependencies group — datahub-project/terraform-provider-datahub0 reactions
- Nov 2, 2026deps: bump acryl-datahub from 1.7.0.17 to 1.7.0.19 — davidouagne/datahub-yaml-source0 reactions
- Nov 2, 2026deps: Bump acryl-datahub from 1.7.0.17 to 1.7.0.19 — davidouagne/datahub-healthdcat-ap-exporter0 reactions · 1 comment
- Nov 2, 2026chore(deps): bump acryl-datahub from 1.7.0.17 to 1.7.0.18 — acryldata/mcp-server-datahub0 reactions · 1 comment
- Nov 2, 2026chore(deps-dev): bump acryl-datahub from 1.7.0.16 to 1.7.0.18 in the python-dev-dependencies group — datahub-project/terraform-provider-datahub0 reactions
- Oct 31, 2026build(deps-dev): bump acryl-datahub from 1.6.0.15 to 1.7.0.18rc1 — Z3X-1337/toxicjoin0 reactions
- Oct 28, 2026:dependabot: uv(deps): Bump acryl-datahub[dbt,glue,postgres] from 1.7.0.14 to 1.7.0.16 — ministryofjustice/data-catalogue0 reactions · 1 comment
- Oct 27, 2026Fix false verification when marker belongs to another entity — leadingproblemsolver/realityhandoff-agent0 reactions
- Oct 26, 2026deps: bump acryl-datahub from 1.7.0.14 to 1.7.0.17 — davidouagne/datahub-yaml-source0 reactions · 1 comment
- Oct 26, 2026deps: Bump acryl-datahub from 1.7.0.16 to 1.7.0.17 — davidouagne/datahub-healthdcat-ap-exporter0 reactions · 1 comment
- Oct 26, 2026build(deps): Bump acryl-datahub from 1.7.0.14 to 1.7.0.16 — davidouagne/datahub-healthdcat-ap-exporter0 reactions · 1 comment
- Oct 26, 2026chore(deps): bump acryl-datahub from 1.7.0.14 to 1.7.0.17 — acryldata/mcp-server-datahub0 reactions
- Oct 26, 2026chore(deps-dev): bump acryl-datahub from 1.7.0.14 to 1.7.0.16 in the python-dev-dependencies group — datahub-project/terraform-provider-datahub0 reactions
- Oct 8, 2026[0.4.0 설계] Schema · Domain Semantic Relations · Ontology-ready Verification — nyangko/Brainprint0 reactions
- Oct 8, 2026[0.3.0 설계] Project Knowledge Catalog · Living Wiki · 근거 기반 문서 — nyangko/Brainprint0 reactions
- Oct 6, 2026:dependabot: uv(deps): Bump acryl-datahub[dbt,glue,postgres] from 1.7.0.13 to 1.7.0.14 — ministryofjustice/data-catalogue0 reactions
- Oct 5, 2026build(deps): Bump acryl-datahub from 1.7.0.13 to 1.7.0.14 — davidouagne/datahub-yaml-source0 reactions
- Oct 5, 2026build(deps): Bump acryl-datahub from 1.7.0.13 to 1.7.0.14 — davidouagne/datahub-healthdcat-ap-exporter0 reactions · 1 comment
- Oct 4, 2026[Feature]: Add DataHub data-source connector — topoteretes/cognee0 reactions · 4 comments
- Oct 1, 2026:dependabot: uv(deps): bump acryl-datahub[dbt,glue,postgres] from 1.7.0.10 to 1.7.0.13 — ministryofjustice/data-catalogue0 reactions
- Sep 29, 2026:dependabot: uv(deps): bump acryl-datahub[dbt,glue,postgres] from 1.7.0.10 to 1.7.0.12 — ministryofjustice/data-catalogue0 reactions · 1 comment
- Sep 28, 2026build(deps): Bump acryl-datahub from 1.7.0.10 to 1.7.0.13 — davidouagne/datahub-yaml-source0 reactions
- Sep 28, 2026build(deps): Bump acryl-datahub from 1.7.0.10 to 1.7.0.13 — davidouagne/datahub-healthdcat-ap-exporter0 reactions · 1 comment
- Sep 8, 2026chore(deps): bump datahub-agent-context from 1.7.0.4 to 1.7.0.9 — edycutjong/antigen0 reactions
- Sep 8, 2026chore(deps): bump acryl-datahub from 1.7.0.4 to 1.7.0.9 — edycutjong/antigen0 reactions
- Aug 19, 2026chore(deps): Bump acryl-datahub from 1.6.0.16 to 1.7.0.4 — AmirmLotfy/zence0 reactions
- Aug 10, 2026feat: add recall skill for forward ML lineage blast radius — datahub-project/datahub-skills0 reactions
- Jul 28, 2026:dependabot: uv(deps): Bump acryl-datahub[dbt,glue,postgres] from 1.6.0 to 1.6.0.15 — ministryofjustice/data-catalogue0 reactions · 1 comment
- Jul 21, 2026feat(ingest/mysql): add performance_schema usage and query lineage — alexjst/datahub0 reactions · 1 comment
- Jul 21, 2026feat(metrics): add metrics autocomplete and infinite scroll — alexjst/datahub0 reactions · 1 comment
- Jun 22, 2026Bump acryl-datahub from 1.2.0.9 to 1.2.0.9.post1 — mozilla/mozilla-datahub-ingestion0 reactions
- May 14, 2026design: add Datahub community source — withcoral/coral0 reactions
- Apr 24, 2026wiki: module grouping collapses real source packages into ~4 pages while generating 10+ pages for IntelliJ .iml files — abhigyanpatwari/GitNexus0 reactions
- Mar 2, 2026Sync upstream datahub changes - 2026-10-19 — National-Node-Net/ndt-data-catalogue0 reactions
- Feb 1, 2026Update acryl-datahub requirement from <0.14.0,>=0.13.0 to >=0.13.0,<1.4.0 in /services/backend-api — chicoryai/chicory0 reactions
- Nov 12, 2025chore(deps): bump io.acryl:datahub-client from 0.15.0-3 to 15.0.4 — apache/cassandra-sidecar0 reactions · 1 comment
- Nov 6, 2025Improve search functionality — ministryofjustice/find-moj-data0 reactions · 6 comments
- Oct 13, 2025PR: 添加DataHub相关镜像 — DaoCloud/public-image-mirror0 reactions · 1 comment
- Jul 17, 2025"GMS is on a newer version than your storage layer" — acryldata/datahub-helm0 reactions · 3 comments
- May 5, 2025[feature] upgrade datahub blueprint to version 1.0 — awslabs/data-on-eks0 reactions · 2 comments
On YouTube · 11
- Jun 25, 2025Flink 2.0 + OpenLineage + DataHub = Lineage Graph — Kentra545 views · 2 comments
- Oct 25, 2026Breakdown: Shipped It? Now Understand It. (Built Hands-Free with Wispr Flow) — Jishanahmed AR Shaikh274 views
- Sep 28, 2023datahub-project/datahub - Gource visualisation — Gourcer62 views
- Aug 10, 2026Antigen — a prompt-injection immune system for DataHub — edycutjong39 views
- Aug 9, 2026Blast Radius — DataHub Agent Hackathon — Ritesh20 views
6 more on YouTube
- Aug 10, 2026Agent Evidence Graph — Verify Agent Releases from Runtime Evidence | Live Demo — Wei Tianyi17 views
- Jul 26, 2026TrustBoard — a trust score that lives in the graph, where the next agent finds it — Kevin Soto16 views
- Aug 7, 2026unmeasured — a DataHub agent that closes the loop: 4 stale alerts, 2 platforms, 1 table to fix — Ciki Zeng15 views
- Jul 29, 2026DecisionGraph — Governed AI Decisions Built on DataHub — DecisionGraph15 views
- Jul 27, 2026DataHub Agent Arbiter — deterministic authority arbitration for AI agents — William Frescas8 views
- Aug 5, 2026LineageGuard: DataHub Schema Migration Risk Agent (60s Demo) — Argonaut Works7 views
On Hacker News · 1
- Feb 24, 2025DataHub: The Data Discovery Platform for the Modern Data Stack2 points
On Bluesky · 1
- Dec 6, 2024acryl-datahub 0.14.1.12 (Production/Stable) A CLI to work with DataHub metadata Unknown author 📒Changelog 📖Documentation 🏠Homepage… — @pypi.bluesky.bot1 likes and repost
On Stack Overflow · 1
- Sep 6, 2023Docker compose 'depends_on' referencing an undeclared service0 votes · 1 answer
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- datahub-web-react/AGENTS.mdAGENTS.md
- docs-website/AGENTS.mdAGENTS.md
- metadata-ingestion/AGENTS.mdAGENTS.md
- smoke-test/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- datahub-web-react/CLAUDE.mdCLAUDE.md
- docs-website/CLAUDE.mdCLAUDE.md
- metadata-ingestion/CLAUDE.mdCLAUDE.md
- smoke-test/CLAUDE.mdCLAUDE.md
- .cursor/rules/datahub-dev.mdcCursor rule
- .cursor/rules/test-review.mdcCursor rule
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 6 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 37
Only pytest tags drive CI today.
- Distinctive: line 54
Every file listing, pruning, validation, and enum generation goes through the script, so the model only does the judgement work: reading …
- Distinctive: line 91
Only process frameworks that have files.
- Very specific: line 93
Run tags.py prune --write for those frameworks, which removes deleted tests' entries and dead globs.
- Distinctive: line 97
Read it and derive its tags per references/tagging.md.
- Distinctive: line 98
If an existing glob already covers it with the right tags, leave the file alone.
- Distinctive: line 101
If several files in one directory share the same tags and that directory has no entries yet, one glob is fine.
- Very specific: line 106
Run tags.py validate and tags.py untagged.
- Very specific: line 125
Run tags.py validate and tags.py untagged.
- Very specific: line 131
Follow references/taxonomy.md to write .github/smart-testing/taxonomy.yaml and, if this repository has one, taxonomy.overlay.yaml.
- Very specific: line 137
Run tags.py validate across all frameworks.
- Very specific: line 140
Run ./gradlew :smoke-test:stackFreePytest, which covers the taxonomy/enum sync test.
- Distinctive: line 145
Don't commit: the user reviews the diff first.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test taxonomy
Smart test selection matches a PR's tags against per-test tags. This skill keeps the tags and the taxonomy behind them current. It edits files only: it never runs the tests it tags, and it never commits.
Files
| File | Role |
.github/smart-testing/taxonomy.yaml | The common vocabulary for every framework. |
.github/smart-testing/taxonomy.overlay.yaml | Optional tags for repo-only features. |
.github/smart-testing/taxonomy-rubric.md | The criteria a good taxonomy meets. |
smoke-test/smart_testing/taxonomy.py | Enum mirror of the taxonomy (generated block). |
smoke-test/smart_testing/taxonomy_overlay.py | Mirror of the overlay tags (generated). |
| references/tagging.md | How to tag one test file. |
| references/taxonomy.md | How to regenerate the taxonomy. |
| Framework | Tag file | Paths relative to | Test files |
pytest | smoke-test/smart_testing/test_tags.yaml | smoke-test/ | tests/e2e/**/test_*.py, tests/e2e/**/*_test.py |
playwright | .github/smart-testing/playwright/test_tags.yaml | repo root | e2e-test/ui/playwright/tests/**/*.spec.ts |
ingestion | .github/smart-testing/ingestion/test_tags.yaml | repo root | metadata-ingestion/tests/**/{test_*,*_test}.py |
Only pytest tags drive CI today. The others are maintained for when their selectors
land. scripts/tags.py holds the real definitions (FRAMEWORKS).
Base and overlay
The base files (taxonomy.yaml, each test_tags.yaml) are shared by repositories that
run the same tests, so they hold only tags and tests every one of them has. Each may have
an optional overlay next to it (taxonomy.overlay.yaml, test_tags.overlay.yaml) for
features and tests only this repository has. Every consumer merges base and overlay.
- An entry goes in the overlay when its test file, or any tag it needs, is overlay-only. Otherwise it goes in the base.
- A new tag goes in the overlay when the feature it names only exists here.
tags.py validatefails when a base entry uses an overlay tag.
Helper script
Every file listing, pruning, validation, and enum generation goes through the script, so the model only does the judgement work: reading tests and choosing tags.
uv run -q --with pyyaml==6.0.3 python ${CLAUDE_SKILL_DIR}/scripts/tags.py <command> [--framework F ...]| Command | Does |
changed [--base B] | This branch's added, modified, and deleted test files, as JSON. |
list | All test files, grouped by directory. |
untagged | Test files that no entry matches. |
prune [--write] | Entries matching no file (deleted paths, dead globs). --write removes them, comments intact. |
validate | Every tag is in the taxonomy under its dimension, and every entry matches a file. Exits 1 on failure. |
enums [--write] | Regenerate taxonomy.py's enum block and taxonomy_overlay.py from the taxonomy yaml files. |
changed works with or without a PR, on any target branch. The base branch is --base,
else the open PR's base, else the repository's default branch. It diffs the merge base against the
working tree and adds untracked files. That covers committed and uncommitted edits,
and excludes anything that landed on the base after the branch forked.
Modes
Parse $ARGUMENTS: the first word is the mode (default tag), then flags.
--framework is repeatable and takes pytest, playwright or ingestion.
tag: new, changed and deleted tests (default)
With --untagged, the files to tag are every test that no entry matches, whether or not
this branch touched it. This is how existing gaps get backfilled. --base doesn't apply.
Get the files:
- By default, run
tags.py changed(plus--base/--frameworkif given). - With
--untagged, runtags.py untagged(plus--framework) and treat every listed file as added.
Only process frameworks that have files. If none do, say so and stop.
- By default, run
- Run
tags.py prune --writefor those frameworks, which removes deleted tests' entries and dead globs. Handle each added or modified file:
- Read it and derive its tags per references/tagging.md.
- If an existing glob already covers it with the right tags, leave the file alone.
- Otherwise add an exact entry, or update the existing one, in the base or the overlay (see Base and overlay).
- If several files in one directory share the same tags and that directory has no entries yet, one glob is fine.
With many files (say more than 25), batch them to subagents the way
retagdoes.- Run
tags.py validateandtags.py untagged. Fix what they report for the files you touched.
retag: regenerate all tags
- Frameworks are
--framework, or all three if it's absent. For each, runtags.py list. Split the directories into batches of about 25 test files. Give each batch to a subagent (Agent tool,
model: "opus"), running them in parallel. Each subagent gets:- the path of
references/tagging.md, which it must read first - its file list
- the framework's path convention
It returns YAML entries only, with globs where a whole directory shares tags.
- the path of
- Rebuild the
tests:sections of the tag file and its overlay from the merged entries, split per Base and overlay, with one# ── <dir>/ ──section per top-level directory in sorted order. Keep the file headers andalways_runexactly as they are. - Run
tags.py validateandtags.py untagged. Both must come back clean. Re-tag anything they flag. - Report the number of entries and tags per dimension, before and after.
taxonomy: regenerate the taxonomy
- Follow references/taxonomy.md to write
.github/smart-testing/taxonomy.yamland, if this repository has one,taxonomy.overlay.yaml. - Report which tags were added, removed and renamed, and which definitions changed, with rationale.
- Run
tags.py enums --write. - Run
tags.py validateacross all frameworks. For each entry that uses a removed or renamed tag, re-tag the files it covers with references/tagging.md. Then validate again. - Run
./gradlew :smoke-test:stackFreePytest, which covers the taxonomy/enum sync test.
Finish
Summarize what changed, per file. List any untaggable tests and any taxonomy gaps you hit. Don't commit: the user reviews the diff first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

