Suggesting Dbt Bouncer Checks
godatadriven/dbt-bouncer
Analyzes a dbt project and suggests dbt-bouncer checks that already pass (for existing projects) or a sensible starter config (for greenfield projects).
Bumps the dbt-artifacts-parser package semver, prepares a PyPI release, and aligns GitHub Releases with version.
Install Package Version Bump
$ npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yu-iskw/dbt-artifacts-parser package-version-bump --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yu-iskw/dbt-artifacts-parser.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/package-version-bump .claude/skills/package-version-bump && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "package-version-bump" agent skill from https://github.com/yu-iskw/dbt-artifacts-parser/tree/main/.claude/skills/package-version-bump into .claude/skills/package-version-bump/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-version-bump", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yu-iskw/dbt-artifacts-parser/tree/main/.claude/skills/package-version-bumpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yu-iskw/dbt-artifacts-parser package-version-bump --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yu-iskw/dbt-artifacts-parser.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/package-version-bump .agents/skills/package-version-bump && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "package-version-bump" agent skill from https://github.com/yu-iskw/dbt-artifacts-parser/tree/main/.claude/skills/package-version-bump into .agents/skills/package-version-bump/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-version-bump", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yu-iskw/dbt-artifacts-parser package-version-bump --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yu-iskw/dbt-artifacts-parser.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/package-version-bump .cursor/skills/package-version-bump && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "package-version-bump" agent skill from https://github.com/yu-iskw/dbt-artifacts-parser/tree/main/.claude/skills/package-version-bump into .cursor/skills/package-version-bump/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-version-bump", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yu-iskw/dbt-artifacts-parser.git --path .claude/skills/package-version-bump--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yu-iskw/dbt-artifacts-parser package-version-bump --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yu-iskw/dbt-artifacts-parser.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/package-version-bump .gemini/skills/package-version-bump && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "package-version-bump" agent skill from https://github.com/yu-iskw/dbt-artifacts-parser/tree/main/.claude/skills/package-version-bump into .gemini/skills/package-version-bump/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-version-bump", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yu-iskw/dbt-artifacts-parser package-version-bumpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yu-iskw/dbt-artifacts-parser.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/package-version-bump .github/skills/package-version-bump && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "package-version-bump" agent skill from https://github.com/yu-iskw/dbt-artifacts-parser/tree/main/.claude/skills/package-version-bump into .github/skills/package-version-bump/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-version-bump", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yu-iskw/dbt-artifacts-parser package-version-bump --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yu-iskw/dbt-artifacts-parser.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/package-version-bump .opencode/skills/package-version-bump && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "package-version-bump" agent skill from https://github.com/yu-iskw/dbt-artifacts-parser/tree/main/.claude/skills/package-version-bump into .opencode/skills/package-version-bump/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "package-version-bump", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
package-version-bump- GitHub stars
- 118
- Token cost
- ~700 tokens
- SKILL.md length
- 277 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Bumps the dbt-artifacts-parser package semver, prepares a PyPI release, and aligns GitHub Releases with version.
- Works in 2 steps: Commit the version change on the branch… → Create a GitHub Release (this triggers…
- The user asks to bump the library version
- SKILL.md covers Trigger scenarios, Not this skill, Single source of truth and Bump the version, plus 4 more sections
- Calls uv, make and uvx
What it does
Package Version Bump is an agent skill from yu-iskw/dbt-artifacts-parser. Bumps the dbt-artifacts-parser package semver, prepares a PyPI release, and aligns GitHub Releases with version. Use when the user asks to bump the library version, prepare a release, tag a version, or ship to PyPI—not for upgrading project dependencies or lockfile pins.
Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics, covering Data pipelines and ETL and Dependency management. It works with dbt, GitHub and Python. The repository describes itself as: A dbt artifacts parser in python. The licence is Apache-2.0.
When your agent uses it
- The user asks to bump the library version
- Prepare a release
- Ship to PyPI—not for upgrading project dependencies
Example prompts
- “Use the package-version-bump skill to bump the dbt-artifacts-parser package semver, prepares a PyPI release, and aligns GitHub Releases with version”
- “/package-version-bump”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Commit the version change on the branch you release from (typically main).
- Create a GitHub Release (this triggers CI publish). Prefer a tag aligned with semver, e.g. v0.14.0 for 0.14.0.
What it can do on your machine
Read from SKILL.md and the folder at commit 0f6e85b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
uvmakeuvx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv and uvx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Package Version Bump loads about 700 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 277 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from yu-iskw/dbt-artifacts-parser at commit 0f6e85b, republished under its Apache-2.0 licence (© yu-iskw). 277 words, ~700 tokens.
Download SKILL.mdSave it as
.claude/skills/package-version-bump/SKILL.md (or your agent's skills folder).- name
- package-version-bump
- description
- Bumps the dbt-artifacts-parser package semver, prepares a PyPI release, and aligns GitHub Releases with __version__. Use when the user asks to bump the library version, prepare a release, tag a version, or ship to PyPI—not for upgrading project dependencies or lockfile pins.
Package Version Bump
Trigger scenarios
Activate this skill when the user says or implies:
- Bump version, release version, next patch/minor/major
- Prepare a release, ship to PyPI, publish the package
- Set version to a specific semver (e.g.
0.14.0) - Tag or GitHub Release in the context of this library’s version
Not this skill
- Dependency / lockfile bumps (e.g. Renovate, “upgrade deps”): use
make upgrade-deps(uv lock --upgrade && uv sync) and edits to pyproject.toml constraints—not__version__in the package.
Single source of truth
- The published package version is
__version__in dbt_artifacts_parser/init.py. - pyproject.toml sets
dynamic = ["version"]and[tool.hatch.version] path = "dbt_artifacts_parser/__init__.py"so the Hatch CLI can bump that file.
Run all commands from the repository root.
Bump the version
Choose one path.
Preferred: Hatch CLI via uvx
The hatch CLI is not a project dev dependency; use ephemeral install:
uvx hatch version patch
# or: uvx hatch version minor
# or: uvx hatch version majorTo set an explicit version:
uvx hatch version 0.14.0Fallback: manual edit
Edit only the __version__ = "..." assignment in dbt_artifacts_parser/init.py.
Verify
- Confirm the string:
uv run python -c 'import dbt_artifacts_parser; print(dbt_artifacts_parser.__version__)' - Optionally:
uv buildand/ormake testbefore releasing.
Ship (PyPI)
Publishing is automated when a GitHub Release is created (workflow publish.yml on release: created → dev/publish.sh).
- Commit the version change on the branch you release from (typically
main). - Create a GitHub Release (this triggers CI publish). Prefer a tag aligned with semver, e.g.
v0.14.0for0.14.0.
Local publish (maintainers): make publish or make test-publish — same scripts as CI; still requires __version__ updated first.
Do not
- Do not rely on a git tag or Release title alone: the wheel/sdist must reflect the updated
__version__or users and PyPI metadata will disagree with the tag.
Optional
- Add
hatchto[project.optional-dependencies].devif you preferuv run hatch version …withoutuvx.
© yu-iskw, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/package-version-bump of yu-iskw/dbt-artifacts-parser.
Open the folder on GitHubat commit 0f6e85b
Compare with similar skills
Package Version Bump next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Package Version Bump this skillyu-iskw/dbt-artifacts-parser | 118 | — | ~700 | Automated safety check: Pass | Apache-2.0 | |
| Suggesting Dbt Bouncer Checksgodatadriven/dbt-bouncer | 135 | — | ~1k | Automated safety check: Pass | MIT | |
| Senior Data Engineerbenchflow-ai/skillsbench | 1.8k | — | ~5.9k | Automated safety check: Pass | MIT | |
| Data Quality Frameworkswshobson/agents | 40k | 10 repos | ~1.1k | Automated safety check: Pass | MIT | |
| New Checkgodatadriven/dbt-bouncer | 135 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Build Artifactsgodatadriven/dbt-bouncer | 135 | — | ~399 | Automated safety check: Pass | MIT |
Similar skills
Senior Data Engineer
benchflow-ai/skillsbench
World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, real-time streaming, and data infrastructure.
Data Quality Frameworks
wshobson/agents
Sets up data quality checks with Great Expectations, dbt tests and data contracts, with checkpoints and pass-fail reports for pipelines.
New Check
godatadriven/dbt-bouncer
Scaffold a new dbt-bouncer check class with tests. An agent skill from godatadriven/dbt-bouncer.
Build Artifacts
godatadriven/dbt-bouncer
Regenerate dbt test fixtures after dbtproject changes. An agent skill from godatadriven/dbt-bouncer.
Senior Data Engineer
alirezarezvani/claude-skills
Data engineering skill for building scalable data pipelines, ETL/ELT systems, and data infrastructure.
More from yu-iskw/dbt-artifacts-parser
Dbt Parser Refresh
yu-iskw/dbt-artifacts-parser
Refreshes dbt artifact schemas from dbt-labs/dbt-core and regenerates Pydantic parser classes.
Related
Categories
Questions about Package Version Bump
What does Package Version Bump do?
Bumps the dbt-artifacts-parser package semver, prepares a PyPI release, and aligns GitHub Releases with version. Package Version Bump is an agent skill from yu-iskw/dbt-artifacts-parser. Bumps the dbt-artifacts-parser package semver, prepares a PyPI release, and aligns GitHub Releases with version.
When should I use Package Version Bump?
Package Version Bump fits situations like: the user asks to bump the library version; prepare a release; ship to PyPI—not for upgrading project dependencies.
How do I install Package Version Bump in Claude Code?
Run `npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a claude-code`. Or copy the skill folder (.claude/skills/package-version-bump in yu-iskw/dbt-artifacts-parser) into .claude/skills/package-version-bump in your project. Claude Code loads it when a task matches its description.
How do I install Package Version Bump in Codex?
Run `npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a codex`. Or copy the skill folder (.claude/skills/package-version-bump in yu-iskw/dbt-artifacts-parser) into .agents/skills/package-version-bump in your project. Codex loads it when a task matches its description.
Can I use Package Version Bump in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yu-iskw/dbt-artifacts-parser --skill package-version-bump -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/package-version-bump, .gemini/skills/package-version-bump, .github/skills/package-version-bump and .opencode/skills/package-version-bump in your project.
What does Package Version Bump need to run?
Going by SKILL.md and its folder, Package Version Bump needs the command-line tools its instructions call (uv, make and uvx). Our summary lists: Python 3.
Does Package Version Bump access the network?
SKILL.md contains no URLs. Its commands use uv and uvx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Package Version Bump safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Package Version Bump use?
Package Version Bump is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Package Version Bump use?
About 700 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Package Version Bump?
Skills that share tags, products or a category with Package Version Bump: Suggesting Dbt Bouncer Checks (godatadriven/dbt-bouncer, 135 stars), Senior Data Engineer (benchflow-ai/skillsbench, 1.8k stars), Data Quality Frameworks (wshobson/agents, 40k stars) and New Check (godatadriven/dbt-bouncer, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Package Version Bump?
yu-iskw (a GitHub user) maintains it in yu-iskw/dbt-artifacts-parser, which has 118 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 24, 2026.
Source: yu-iskw/dbt-artifacts-parser on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.