reopt-eav

Manage EAV schema drift, synchronization, and file-based migrations for Brandapp projects.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/reopt-ai/reopt-skills --skill reopt-eav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reopt-eav
Source: https://github.com/reopt-ai/reopt-skills/tree/main/skills/reopt-eav
Command: npx skills add https://github.com/reopt-ai/reopt-skills --skill reopt-eav

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires reopt-cli, reopt-brandapp, and includes references (resource) components.

What problem does it solve?

This Skill helps you review, synchronize, and migrate Brandapp EAV schemas without accidentally applying unsafe or unreviewed changes.

Core Features & Use Cases

  • Drift detection and sync: Compare local schema files with server state, preview changes, and apply updates safely.
  • Schema recovery and review: Pull server state back into eav.schema.ts, generate markdown diffs, and validate planned changes in CI or development.
  • File-based migrations: Plan, run, inspect history, and verify EAV migrations with guardrails for destructive operations like orphan deletion.
  • Use Case: A developer updates entity fields locally, reviews the drift report, previews deletions, and then syncs only after confirming the change is safe.

Quick Start

Ask the agent to check EAV schema drift and preview any required sync or migration steps for the current Brandapp project.

Frequently Asked Questions about reopt-eav

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

FAQPage Schema
How do I detect and sync EAV schema drift in a Brandapp project?

To detect EAV schema drift, compare local schema files against the server state to preview pending updates. You can then safely sync changes only after confirming the drift report and previewing any destructive operations.

What is the best way to review server EAV schema changes locally?

The best way to review server EAV schema changes is to pull the server state back into your local eav.schema.ts file. This generates a markdown diff for validation in CI or local development before applying updates.

How do I safely run file-based EAV migrations with orphan deletion?

To safely run file-based EAV migrations with orphan deletion, use guardrails like dry-run previews and lock-based execution. This prevents accidental application of unreviewed or destructive schema changes during the migration workflow.

Do I need reopt CLI to manage Brandapp EAV schema synchronization?

Yes, you need reopt CLI and the Brandapp SDK because EAV schema synchronization requires compatibility with their specific rules. The schema management workflow is designed to operate directly within this CLI environment.

Can I validate planned EAV schema changes in CI before applying them?

Yes, you can validate planned EAV schema changes in CI by pulling the server state and generating markdown diffs. This allows you to review drift and preview required sync or migration steps before execution.