database-migration
The database-migration command provides a structured workflow for executing database schema changes and creating migration files. Use this command when modifying database schemas, generating migration files, or updating type definitions related to schema changes in the everything-claude-code repository, following a sequence that emphasizes understanding current state, making minimal coherent changes, and verifying modifications.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/affaan-m/ECC/HEAD/.claude/commands/database-migration.md -o ~/.claude/commands/database-migration.mddatabase-migration.md
# /database-migration Use this workflow when working on **database-migration** in `everything-claude-code`. ## Goal Database schema changes with migration files ## Common Files - `**/schema.*` - `migrations/*` ## Suggested Sequence 1. Understand the current state and failure mode before editing. 2. Make the smallest coherent change that satisfies the workflow goal. 3. Run the most relevant verification for touched files. 4. Summarize what changed and what still needs review. ## Typical Commit Signals - Create migration file - Update schema definitions - Generate/update types ## Notes - Treat this as a scaffold, not a hard-coded script. - Update the command if the workflow evolves materially.
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
>
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
>
Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
>