skills.rest
astroville
astrovilleOFFICIAL
Explore all skills by this author →
GitHub

database-stack

Guides schema design, migrations, indexing, and rollout safety for database changes.

Updated Apr 20, 2026
Search Tags:#indexing#schema design#database#migrations#queries#backfill#rollout safety
One-click install
npx skills add https://github.com/astroville/sprout --skill database-stack-astroville
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-stack
Source: https://github.com/astroville/sprout/tree/main/.claude/skills/database-stack
Command: npx skills add https://github.com/astroville/sprout --skill database-stack-astroville

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Database changes are risky operational events: destructive migrations, missing indexes, and poorly sequenced deploys can cause outages or data loss. This Skill provides structured guidance so schema and data changes are planned, reviewed, and rolled out safely. ## Core Features & Use Cases - Migration Planning: Promotes additive, phased migrations and flags expensive or destructive changes before they ship. - Query and Index Review: Watches query shape, index tradeoffs, and lock behavior during schema design. - Safe Rollout Sequencing: Coordinates application deploys with data changes, and designs backfills that are resumable and idempotent. - Use Case: When adding a new column that requires backfilling millions of rows, use this Skill to plan a phased migration with a rollback path instead of a single risky deploy. ## Quick Start Ask the assistant to review your planned database migration and rollout plan using the database-stack guidance before deploying it.

Frequently Asked Questions about database-stack

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

FAQPage Schema
How do I plan a safe database migration for production?▼

Plan additive, phased migrations rather than destructive ones, and sequence application deploys with data changes explicitly. Flag expensive migrations early and define a rollback plan before applying any destructive change.

How to design a database backfill that can resume after failure?▼

Design backfills to be resumable and idempotent so rerunning them after a failure does not corrupt data. Track progress externally and make each batch safe to repeat.

What should I check before adding a database index?▼

Evaluate query shape, index tradeoffs, and lock behavior before adding an index. Indexes speed reads but add write overhead and can lock tables during creation on large datasets.

When should I avoid destructive schema changes?▼

Avoid destructive changes like dropping columns or tables without a clear deployment and rollback plan. Prefer deprecating in phases: stop writing, verify no reads remain, then remove in a later release.

Why do database migrations cause downtime during deploys?▼

Downtime happens when schema changes are incompatible with the running application version or when migrations hold locks on hot tables. Phased, additive changes let old and new code coexist during rollout.

Related Skills

Explore More Software Engineering Skills→
Pixel-Process-UGPixel-Process-UG
1

database-schema-design

Design and optimize relational and NoSQL database schemas with indexing and migration strategies.

Official
Advanced
mymx2mymx2
4

schema-migration-planner

Plan zero-downtime database schema migrations for Kotlin and Spring systems.

Community
Advanced
Impertio-StudioImpertio-Studio

postgres-impl-query-performance-toolkit

Analyze PostgreSQL EXPLAIN plans to diagnose slow queries and lock waits.

Official
Advanced
jeremybrasherjeremybrasher

principle-outcome-oriented-execution

Guides planned rewrites and migrations toward target architecture with explicit verification boundaries.

Community
Intermediate