Skip to content
TrustedSkillsbeta
Back to all skills

Database Migration Integrity Checker

Checked
jorgealves·vlatest·database·GPL-3.0

Helps with database, migration as part of working with databases and data persistence workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jorgealves/agent_skills --skill database-migration-integrity-checker -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jorgealves

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jorgealves/agent_skills at 85014ad37d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
85014ad37d
Manifest
database-migration-integrity-checker/SKILL.md
Scanned
2 files, 65 lines
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 validates data consistency and structural integrity during database migration operations. It helps ensure that schema changes, data transformations, or table migrations complete without corruption or loss of information.

When to use it

  • Before executing production database migration scripts to prevent data loss
  • After running automated migration tools to verify successful completion
  • When upgrading database versions with complex schema modifications
  • During CI/CD pipelines that include database version updates

Key capabilities

  • Detects missing or mismatched columns after migration
  • Identifies orphaned records during table restructuring
  • Validates foreign key relationships post-migration
  • Reports integrity violations before they impact production systems

Example prompts

"Run an integrity check on my PostgreSQL migration from v12 to v15." "Validate that all user data was preserved after the schema update." "Check for orphaned records in the orders table after migrating customer IDs."

Tips & gotchas

  • Ensure you have a backup before running integrity checks on production databases.
  • Some migrations may require specific database drivers installed beforehand.