openspec-schema-version-collision

Aligns OpenSpec schema definitions and metadata with actual repository state.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill openspec-schema-version-collision
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-schema-version-collision
Source: https://github.com/quaid-app/quaid/tree/main/.squad/skills/openspec-schema-version-collision
Command: npx skills add https://github.com/quaid-app/quaid --skill openspec-schema-version-collision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change proposals often propose a schema target that no longer matches the shipped repository, causing drift between the intended design and the live codebase. This Skill provides a disciplined workflow to detect, align, and repair schema-version mismatches before implementation proceeds.

Core Features & Use Cases

  • Verify the live schema target before batching to ensure that all artifacts reflect the current SCHEMA_VERSION and column definitions.
  • Truth-repair all change artifacts together (proposal, design, tasks, specs) to avoid conflicting truths after review.
  • Resolve logical-name versus physical-name drift by validating field mappings and performing explicit renames when necessary.
  • Freeze progress on misaligned changes and re-route review once the baseline truth is restored to ensure safe deployments.

Quick Start

Run the OpenSpec truth-repair workflow against the current repository to align schema targets with the live codebase.

Frequently Asked Questions about openspec-schema-version-collision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix OpenSpec schema drift after a version bump collides with shipped artifacts?▼

Repair OpenSpec schema drift by verifying the live SCHEMA_VERSION and actual column and index names in src/schema.sql, aligning all proposal, design, and tasks artifacts to match the repository's current state.

What is schema-version collision repair in a live repository?▼

Schema-version collision repair detects when OpenSpec proposals target a schema that no longer matches the shipped repository, aligns drifted artifacts to the live schema, and records drift corrections to restore a single source of truth.

How do I align OpenSpec proposals, designs, and tasks packages with the actual src/schema.sql definitions?▼

Run a truth-repair workflow that batch-aligns proposals, designs, tasks, and specs against src/schema.sql, validating field mappings and performing explicit renames to resolve logical-name versus physical-name drift.

When should I freeze progress on an OpenSpec change proposal?▼

Freeze progress on an OpenSpec change when schema targets misalign with the live repository's actual schema, re-routing review only after baseline truth is restored to ensure safe deployments.

Does this schema migration workflow handle logical-name versus physical-name drift in DDL alignment?▼

Yes, the workflow validates field mappings between logical and physical names during DDL alignment, performing explicit renames when necessary to correct drift across version bumps and migrations.

Can I use this truth-repair process for code review on schema migrations?▼

Yes, the truth-repair process enforces verifying SCHEMA_VERSION and actual column and index names before batching, ensuring all artifacts reflect current definitions for accurate code review on schema migrations.