schema-sync

Detect database schema changes and update related documentation and code.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/matchacone/pickle-LARP --skill schema-sync-matchacone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-sync
Source: https://github.com/matchacone/pickle-LARP/tree/main/.agent/skills/schema-sync
Command: npx skills add https://github.com/matchacone/pickle-LARP --skill schema-sync-matchacone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that changes to a database schema are propagated across all related documentation and code, preventing inconsistencies and errors.

Core Features & Use Cases

  • Schema Propagation: Automatically updates documentation and code when the database schema changes.
  • Change Detection: Identifies schema changes in the source file and triggers updates.
  • Use Case: Use this Skill after making changes to the database schema to ensure all downstream artifacts are updated accordingly.

Quick Start

Run the schema-sync skill with the argument for the table or change description you want to propagate.

Frequently Asked Questions about schema-sync

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

FAQPage Schema
How do I synchronize database schema changes across documentation and code?

Database schema synchronization propagates schema changes to related documentation and code automatically. You provide the specific table or change description, and the skill detects source changes to maintain consistency across all downstream artifacts.

What is the best way to automate database consistency after modifying a table?

Automating database consistency requires detecting schema file changes and updating related code and documentation. This skill triggers updates automatically after you input the specific table or change description, preventing inconsistencies and errors.

How do I keep database documentation updated when the schema changes?

Keeping database documentation updated involves propagating schema changes from the source file to all related artifacts. By running the synchronization process with the change description, documentation is automatically updated to match the new schema.

Do I need to manually input changes to update database schema documentation?

Manual input is required to specify the table or change description for the synchronization process. Once provided, the skill detects the schema changes and automatically updates the related code and documentation.

When should I use a schema synchronization tool for software maintenance?

Schema synchronization tools should be used immediately after making changes to a database schema. They ensure all downstream code and documentation are updated accordingly, preventing inconsistencies during software maintenance.

What are the limitations of automating database schema synchronization?

Automating database schema synchronization requires manual input for the specific table or change description to trigger updates. It focuses on propagating changes to existing documentation and code rather than generating new schema designs.