Run any Skill in Manus with one click

dbt-parser-refresh

Stars0

Forks0

UpdatedMay 8, 2026 at 00:30

Regenerates TypeScript types from dbt artifact JSON schemas. Use when the user asks to update parsers, sync with upstream, refresh types, or regenerate parser types from existing schemas.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

yu-iskw

yu-iskw/dbt-artifacts-parser-ts

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	dbt-parser-refresh
description	Regenerates TypeScript types from dbt artifact JSON schemas. Use when the user asks to update parsers, sync with upstream, refresh types, or regenerate parser types from existing schemas.
compatibility	Requires pnpm, Node.js

dbt Parser Refresh

Trigger scenarios

Activate this skill when the user says or implies:

Refresh parsers, update parsers, sync parsers
Update from dbt-core, sync with upstream dbt-core
Regenerate TypeScript types, regenerate parser types, run codegen
Download dbt schemas, pull schemas from dbt-core (note: this repo has no download script; schemas live in resources/)

Scripts and paths

Run commands from the repository root.
Generate (only): Regenerate TypeScript types from existing JSON schemas under packages/dbt-artifacts-parser/resources/json-schema/ (and legacy resources/<category>/ when used).
- From repo root: pnpm --filter dbt-artifacts-parser gen:types or bash packages/dbt-artifacts-parser/scripts/generate.sh
- From package: cd packages/dbt-artifacts-parser && pnpm gen:types
Schema location: packages/dbt-artifacts-parser/resources/json-schema/{catalog,manifest,run-results,sources,semantic_manifest}/ (JSON Schemas for codegen; kept separate from resources/manifest/ etc. so fixture discovery does not treat schemas as artifacts). Each *_vN.json file is turned into src/<category>/vN.ts. Legacy resources/<category>/ is still accepted for catalog/sources when present.
Artifact categories: catalog, manifest, run-results, sources, semantic_manifest.
The generate script does not accept artifact_type or version arguments; it processes all *_vN.json files in each category directory.
Removing a schema: delete the matching src/<category>/vN.ts yourself (partial regen does not delete absent versions). When adding a new major version, update hand-maintained src/<category>/index.ts (exports, Parsed* unions, parse helpers).
Root src/index.ts: still regenerated by generate.sh (catalog re-export); category index.ts files are not overwritten.

Adding new schemas

This repo has no download script. To add new schema versions, copy JSON schema files (e.g. from dbt-labs/dbt-core under schemas/dbt/ on GitHub raw, or https://schemas.getdbt.com/) into the appropriate packages/dbt-artifacts-parser/resources/json-schema/<category>/ directory (use *_vN.json filenames), then run the generate command above.

Example

Full regenerate (all categories and versions):

pnpm --filter dbt-artifacts-parser gen:types

Or from repo root using the script directly:

bash packages/dbt-artifacts-parser/scripts/generate.sh

More from this repository

same repository

dependency-upgrade

yu-iskw/dbt-artifacts-parser-ts

Upgrade outdated npm dependencies in the pnpm monorepo (recursive update, latest, targeted packages). Use when the user asks to upgrade dependencies, bump packages, refresh lockfile, pnpm update, outdated packages, latest versions, or dependency refresh—not monorepo release versions.

2026-05-140

lint-fix

yu-iskw/dbt-artifacts-parser-ts

Format code, run linters and static analysis, and find unused code (ESLint + Knip). Use when the user asks to fix lint, format code, run formatters, find dead code, unused exports, run knip, fix style, tidy code, or run eslint --fix.

2026-05-140

manage-adr

yu-iskw/dbt-artifacts-parser-ts

Manage Architecture Decision Records (ADRs). Use this to initialize, create, list, and link ADRs to document architectural evolution. Requires 'adr-tools' to be installed.

2026-05-140

postmortem

yu-iskw/dbt-artifacts-parser-ts

Use at the end of a coding session to summarize outcomes, failures, inefficiencies, and root causes, then output a concise postmortem report with ranked improvements for next time. Output only in chat; do not edit project files unless the user explicitly asks. Skip nit-picks and one-off mistakes.

2026-05-140

version-bump

yu-iskw/dbt-artifacts-parser-ts

Interactively bump package versions for the parser package. Use when the user asks to bump version, increment version, set release version, or release dbt-artifacts-parser.

2026-05-140

deep-problem-solving

yu-iskw/dbt-artifacts-parser-ts

Interactive deep research and decision support: frame the real problem (XY-aware), ask exactly 10 multiple-choice questions one at a time, then produce a rigorous comparative evaluation (default 5 approaches, 0–100 scores) and recommendation. Use when the user wants structured discovery before committing to a solution, a scored comparison of approaches, or to avoid jumping straight to an answer—especially for architecture, strategy, or high-stakes trade-offs.

2026-04-130

name	dbt-parser-refresh
description	Regenerates TypeScript types from dbt artifact JSON schemas. Use when the user asks to update parsers, sync with upstream, refresh types, or regenerate parser types from existing schemas.
compatibility	Requires pnpm, Node.js

dbt Parser Refresh

Trigger scenarios

Activate this skill when the user says or implies:

Refresh parsers, update parsers, sync parsers
Update from dbt-core, sync with upstream dbt-core
Regenerate TypeScript types, regenerate parser types, run codegen
Download dbt schemas, pull schemas from dbt-core (note: this repo has no download script; schemas live in resources/)

Scripts and paths

Run commands from the repository root.
Generate (only): Regenerate TypeScript types from existing JSON schemas under packages/dbt-artifacts-parser/resources/json-schema/ (and legacy resources/<category>/ when used).
- From repo root: pnpm --filter dbt-artifacts-parser gen:types or bash packages/dbt-artifacts-parser/scripts/generate.sh
- From package: cd packages/dbt-artifacts-parser && pnpm gen:types
Schema location: packages/dbt-artifacts-parser/resources/json-schema/{catalog,manifest,run-results,sources,semantic_manifest}/ (JSON Schemas for codegen; kept separate from resources/manifest/ etc. so fixture discovery does not treat schemas as artifacts). Each *_vN.json file is turned into src/<category>/vN.ts. Legacy resources/<category>/ is still accepted for catalog/sources when present.
Artifact categories: catalog, manifest, run-results, sources, semantic_manifest.
The generate script does not accept artifact_type or version arguments; it processes all *_vN.json files in each category directory.
Removing a schema: delete the matching src/<category>/vN.ts yourself (partial regen does not delete absent versions). When adding a new major version, update hand-maintained src/<category>/index.ts (exports, Parsed* unions, parse helpers).
Root src/index.ts: still regenerated by generate.sh (catalog re-export); category index.ts files are not overwritten.

Adding new schemas

Example

Full regenerate (all categories and versions):

pnpm --filter dbt-artifacts-parser gen:types

Or from repo root using the script directly:

bash packages/dbt-artifacts-parser/scripts/generate.sh