data-contract-migrations — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited data-contract-migrations (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.
Use this skill when data shape changes can break reads, writes, reports, tenants, or integrations. The goal is an explicit compatibility and migration plan, not just a SQL diff.
Gather these facts before proposing changes:
If the current data does not contain a field, treat it as absent. Do not invent fallback fields.
Use expand-migrate-contract for production systems:
For small systems, a direct migration is acceptable only when downtime, rollback, and data loss risks are explicitly low.
Every plan must include:
contract_change:
affected_readers_writers:
migration_strategy:
backfill_plan:
rollback_or_recovery:
tenant_and_security_checks:
verification_queries:
test_commands:
release_gate:Raise errors for missing critical data rather than warning and falling back to incomplete output.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.