New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Version Management

by relytcloud in relytcloud/pg_ducklake

Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch).

MITAuto-check passedDevelopment

Install Version Management

skills CLI
$ npx skills add relytcloud/pg_ducklake --skill version-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install relytcloud/pg_ducklake version-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/relytcloud/pg_ducklake.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/version-management .claude/skills/version-management && rm -rf skills-src

Use ~/.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/

Facts

Skill name
version-management
GitHub stars
143
Token cost
~455 tokens
SKILL.md length
213 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch).

  • Works in 3 steps: Push branch: git branch vX.Y main && git… → Push tag: git tag vX.Y.0 vX.Y && git… → Bump main to the next dev version…
  • Tasks that involve Debugging
  • SKILL.md covers Cut a minor release vX.Y.0, Ship a patch vX.Y.Z (Z > 0) and Version touchpoints
  • Calls git

What it does

Version Management is an agent skill from relytcloud/pg_ducklake. Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch). MUST consult when: deciding a version number, cutting a release, creating a version tag, opening a release/patch branch, or backporting a bug fix.

Its SKILL.md is about 460 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 Development, covering Debugging. It works with PostgreSQL, Git and SQL. The repository describes itself as: Native lakehouse experience in Postgres powered by DuckDB & Ducklake. The licence is MIT.

When your agent uses it

  • Tasks that involve Debugging

Example prompts

  • “/version-management”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Push branch: git branch vX.Y main && git push origin vX.Y
  2. Push tag: git tag vX.Y.0 vX.Y && git push origin vX.Y.0 (release CI runs)
  3. Bump main to the next dev version (vX.(Y+1).0, or v(X+1).0.0 if a

What it can do on your machine

Read from SKILL.md and the folder at commit bc5d4b4. 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:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Version Management loads about 455 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 213 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~455

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 relytcloud/pg_ducklake at commit bc5d4b4, republished under its MIT licence (© relytcloud). 213 words, ~455 tokens.

Download SKILL.mdSave it as .claude/skills/version-management/SKILL.md (or your agent's skills folder).
name
version-management
description
Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch). MUST consult when: deciding a version number, cutting a release, creating a version tag, opening a release/patch branch, or backporting a bug fix.

Version Management

Semantic versioning v<major>.<minor>.<patch>: major = breaking, minor = new feature, patch = bug fix only. The git tag (vX.Y.Z) and the extension's default_version always agree.

  • main -- next unreleased version; takes anything.
  • branch vX.Y -- one per minor line; bug fixes only, never features.
  • tag vX.Y.Z -- one per patch; immutable. Fix a bad release with a new patch tag, never by re-tagging. Pushing a v* tag is what fires release CI.

Cut a minor release vX.Y.0

Version touchpoints are already X.Y.0 on main (bumped after the previous release). Then three things:

  1. Push branch: git branch vX.Y main && git push origin vX.Y
  2. Push tag: git tag vX.Y.0 vX.Y && git push origin vX.Y.0 (release CI runs)
  3. Bump main to the next dev version (vX.(Y+1).0, or v(X+1).0.0 if a breaking change has landed) -- see touchpoints below.

Ship a patch vX.Y.Z (Z > 0)

  1. Land the fix on main first if the bug is there too; cherry-pick onto each affected vX.Y branch.
  2. On the vX.Y branch, bump touchpoints to X.Y.Z.
  3. Push tag vX.Y.Z (release CI runs).

Version touchpoints

Per bump, in one commit:

  • pg_ducklake/pg_ducklake.control -- default_version.
  • pg_ducklake/sql/pg_ducklake--<old>--<X.Y.Z>.sql -- update script (empty placeholder if the release has no SQL object changes).

Keep one base install script (pg_ducklake--1.0.0.sql); PostgreSQL reaches default_version by installing it and applying the --<old>--<new> chain.

© relytcloud, MIT. 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 .agents/skills/version-management of relytcloud/pg_ducklake.

Open the folder on GitHubat commit bc5d4b4

Compare with similar skills

Version Management 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.

Version Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Version Management this skillrelytcloud/pg_ducklake143—~455Automated safety check: PassMIT
Mz PR ReviewMaterializeInc/materialize6.4k—~1.6kAutomated safety check: NotesCustom licence
Trace And Isolaterohitg00/skillkit1.5k—~1.8kAutomated safety check: PassApache-2.0
Supabase Advanced Troubleshootingjeremylongshore/tons-of-skills-marketplace2.8k—~2.8kAutomated safety check: PassMIT
Safe SQL Executionsupabase/supabase111k—~4.2kAutomated safety check: PassApache-2.0
Golang Databaseunxed/f42412 repos~2.9kAutomated safety check: PassMIT

Similar skills

  • Mz PR Review

    MaterializeInc/materialize

    Local code review of current branch vs Materialize standards.

    6.4k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check: notes

  • Trace And Isolate

    rohitg00/skillkit

    Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code.

    1.5k GitHub stars~1.8k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • Supabase Advanced Troubleshooting

    jeremylongshore/tons-of-skills-marketplace

    Deep Supabase diagnostics: pgstatstatements for slow queries, lock debugging with pglocks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop…

    2.8k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Safe SQL Execution

    supabase/supabase

    Official

    A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…

    111k GitHub stars~4.2k tokensUpdated today
    DatabasesAuto-check passed

  • Golang Database

    unxed/f4

    Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context…

    241 GitHub starsUsed in 2 repos~2.9k tokens
    DatabasesAuto-check passed

  • Debugging and Error Recovery

    addyosmani/agent-skills

    Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.

    103k GitHub starsUsed in 1 repo~2.6k tokens
    DevelopmentAuto-check passed

More from relytcloud/pg_ducklake

  • Bump Up Ducklake

    relytcloud/pg_ducklake

    Safely bump pgducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result.

    143 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Setup Dev

    relytcloud/pg_ducklake

    Dev environment setup for build tools, PostgreSQL, submodules, and worktrees.

    143 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check: notes

  • Commit And PR Guidelines

    relytcloud/pg_ducklake

    Commit message conventions and pull request description guidelines.

    143 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check: notes

Works with

Categories

Questions about Version Management

What does Version Management do?

Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch). Version Management is an agent skill from relytcloud/pg_ducklake. Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch).

When should I use Version Management?

Version Management fits situations like: tasks that involve Debugging.

How do I install Version Management in Claude Code?

Run `npx skills add relytcloud/pg_ducklake --skill version-management -a claude-code`. Or copy the skill folder (.agents/skills/version-management in relytcloud/pg_ducklake) into .claude/skills/version-management in your project. Claude Code loads it when a task matches its description.

How do I install Version Management in Codex?

Run `npx skills add relytcloud/pg_ducklake --skill version-management -a codex`. Or copy the skill folder (.agents/skills/version-management in relytcloud/pg_ducklake) into .agents/skills/version-management in your project. Codex loads it when a task matches its description.

Can I use Version Management 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 relytcloud/pg_ducklake --skill version-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-management, .gemini/skills/version-management, .github/skills/version-management and .opencode/skills/version-management in your project.

What does Version Management need to run?

Going by SKILL.md and its folder, Version Management needs the command-line tools its instructions call (git).

Does Version Management access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Version Management 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 Version Management use?

Version Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Version Management use?

About 455 tokens (SKILL.md is roughly 1.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 Version Management?

Skills that share tags, products or a category with Version Management: Mz PR Review (MaterializeInc/materialize, 6.4k stars), Trace And Isolate (rohitg00/skillkit, 1.5k stars), Supabase Advanced Troubleshooting (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Safe SQL Execution (supabase/supabase, 111k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Version Management?

relytcloud (a GitHub organization) maintains it in relytcloud/pg_ducklake, which has 143 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 26, 2026.

Source: relytcloud/pg_ducklake on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.