Skip to content
TrustedSkillsbeta
Back to all skills
Not found in its repository. We could not find this skill in its repository when we last checked (ff7b304, 1 Nov 2026). It is left out of listings and search until a later check finds it again.

Database Versioning

Listed
yonatangross·vlatest·database·MIT

Track database schema changes over time, enabling rollback, auditing, and efficient development workflows.

Repository

Install on your platform

This skill no longer installs under the name database-versioning. yonatangross/orchestkit has no skill named "database-versioning" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-11-01. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

yonatangross

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. none of the 228 skills in the repository match this slug — it was most likely renamed or removed upstream after the registry indexed it Source recorded as yonatangross/orchestkit.
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill facilitates tracking and managing changes to a database schema over time. It allows for creating, applying, and reverting database versions, enabling controlled evolution of data structures. This is crucial for maintaining compatibility between applications and databases during updates or rollbacks.

When to use it

  • Database migrations: Automate the process of updating a database schema from one version to another.
  • Rollback scenarios: Quickly revert a database to a previous, stable state in case of errors after an upgrade.
  • Development and testing: Easily create and manage multiple versions of a database for different development or testing environments.
  • Collaboration: Ensure consistent database structure across teams working on the same project.

Key capabilities

  • Database version creation
  • Database version application
  • Database version rollback

Example prompts

  • "Create a new database version with table 'users' having columns 'id', 'name', and 'email'."
  • "Apply version 3 of the database schema."
  • "Rollback the database to version 1."

Tips & gotchas

This skill requires familiarity with database concepts and schema design. Ensure you have proper backups before applying or rolling back any database versions.