supabase-transmuter

To migrate legacy knowledge base entries in Supabase, this Skill archives original content into a history table and updates records with versioned state and provenance metadata. It scans for out-of-date entries, generates diffs for review, and commits the transformed content back to the canonical table.

Canonization for Supabase knowledge base records is the process of transforming legacy entries into standardized, versioned metadata. It involves archiving original content to a history table and updating the target row with new content, title, and structured metadata for traceability.

Yes, canonizing knowledge entries requires Supabase credentials via the SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY environment variables. The process performs deterministic CLI operations against the knowledge_base and knowledge_history tables using these credentials.

Diff generation for Supabase knowledge base updates produces a human-readable comparison between legacy and canonized content. This mechanism supports change validation by allowing you to review the exact modifications before committing the transformed content back to the database.

The best way to archive original content before updating Supabase records is using a transmutation workflow that safely moves the existing data into a history table. This approach preserves provenance metadata before applying updates to the canonical knowledge base table.

Yes, you can batch scan Supabase rows for out-of-date metadata by retrieving records that exclude a specific legacy version marker in their JSON metadata. This identifies entries needing canonization within batch refactoring workflows.