Menu
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/godatadriven/dbt-bouncer --skill build-artifactsO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Analyzes a dbt project and suggests dbt-bouncer checks that already pass (for existing projects) or a sensible starter config (for greenfield projects). Use when adding dbt-bouncer to a project, creating or extending a dbt-bouncer.yml config, or enforcing dbt conventions with dbt-bouncer.
Scaffold a new dbt-bouncer check class with tests
Baseado na classificação ocupacional SOC
Exibindo SKILL.md
| name | build-artifacts |
| description | Regenerate dbt test fixtures after dbt_project changes |
Regenerate test fixture files after making changes to the dbt project in dbt_project/.
dbt_project/mise run build-artifacts
This generates fixtures for dbt 1.12 and 2.0 in tests/fixtures/dbt_112/target/ and tests/fixtures/dbt_20/target/ (manifest.json, catalog.json, run_results.json). The dbt 1.7–1.11 fixtures are frozen: they stay committed for backward-compat parsing coverage but are no longer rebuilt.
Note: mise.toml uses specific dbt-duckdb version pins. Do not modify the version pins in mise.toml without understanding the compatibility matrix.
Check that the generated files exist and are non-empty. catalog.json is built by introspecting the DuckDB database, so a fixture built without the preceding dbt build step silently ends up with an empty nodes object and every catalog check then passes vacuously — check the node count, not just the file size:
for v in dbt_112 dbt_20; do
python -c "import json;c=json.load(open('tests/fixtures/$v/target/catalog.json'));print('$v', len(c['nodes']), 'catalog nodes')"
done
mise run test
All tests should pass with the new fixtures. If tests fail, check whether the fixture schema changed in a way that requires test updates.