migrate-validate — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited migrate-validate (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Validate all pending database migrations for correctness, safety, and adherence to best practices.
Before applying migrations to catch issues early -- foreign key references to non-existent tables, missing rollback SQL, destructive operations without safeguards, and naming convention violations.
Glob to list all migration files, cross-reference with applied history via mcp__claude-flow__memory_search --namespace migrations (or memory_list) to identify pending ones. The memory_* tool family routes by namespace; agentdb_hierarchical-* does NOT (it routes by tier), so use memory_* here.Read to load each pending .up.sql and .down.sql file and parse the SQL statementsidx_table_column conventionmcp__claude-flow__agentdb_pattern-store with type: 'migration-validation'. No namespace arg — ReasoningBank routes it.mcp__claude-flow__memory_store --namespace migrations for validation results tied to a specific migration number.npx @claude-flow/cli@latest memory search --query "migration validation results" --namespace migrations~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.