database-changes

Manage and apply idempotent PostgreSQL schema changes for Clarin CRM.

Updated Feb 12, 2026

Search Tags:#database #postgresql #schema #migration #sql #clarin

Ready to run

npx skills add https://github.com/ricardoalejandro/clarin --skill database-changes-ricardoalejandro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-changes
Source: https://github.com/ricardoalejandro/clarin/tree/main/.github/skills/database-changes
Command: npx skills add https://github.com/ricardoalejandro/clarin --skill database-changes-ricardoalejandro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured and safe way to modify the Clarin CRM's PostgreSQL database schema, ensuring data integrity and application compatibility.

Core Features & Use Cases

Schema Evolution: Add new tables, columns, and indexes to the database.
Data Integrity: Ensure migrations are idempotent and use safe SQL practices.
Use Case: When adding a new feature that requires storing user preferences, you would use this Skill to create a new user_preferences table with the necessary columns and constraints.

Quick Start

Use the database-changes skill to add a new column named 'status' to the 'leads' table.

Frequently Asked Questions about database-changes

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

FAQPage Schema

How do I add a new column to a PostgreSQL database schema safely?▼

To add a new column to a PostgreSQL database schema safely, you apply idempotent SQL statements that ensure data integrity and application compatibility. This approach prevents errors if the migration runs multiple times.

What is the best way to manage PostgreSQL schema migrations for a CRM?▼

Managing PostgreSQL schema migrations for a CRM requires structured SQL changes that align database evolution with application entity updates. This ensures new tables, columns, and indexes integrate smoothly without breaking existing repository queries.

Can I create junction tables and indexes in PostgreSQL without data loss?▼

Yes, creating junction tables and indexes in PostgreSQL without data loss is possible using safe SQL practices and idempotent statements. This ensures schema evolution maintains data integrity during structural modifications.

How do I make PostgreSQL schema changes idempotent?▼

Making PostgreSQL schema changes idempotent involves writing SQL statements that can execute repeatedly without causing errors or duplicating data. This is essential for reliable schema evolution and maintaining application compatibility.

When do I need to update the database schema for application entity changes?▼

You need to update the database schema for application entity changes when adding new features that require storing persistent data, such as creating a user preferences table with necessary columns and constraints.

Does this database migration approach work with PostgreSQL only?▼

Yes, this database migration approach is designed specifically for PostgreSQL instances. It targets the Clarin CRM database and uses PostgreSQL-specific safe SQL practices to manage schema evolution.