office-drizzle-guardian

Validate Drizzle schema and Railway PostgreSQL changes before applying migrations.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/createtree2017/createtree-office --skill office-drizzle-guardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-drizzle-guardian
Source: https://github.com/createtree2017/createtree-office/tree/main/.agents/skills/office-drizzle-guardian
Command: npx skills add https://github.com/createtree2017/createtree-office --skill office-drizzle-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents production outages and inconsistent app behavior caused by unsafe or incomplete Drizzle schema and migration changes against Railway-hosted PostgreSQL.

Core Features & Use Cases

  • Change-safety guardrails: Aligns server/src/db/schema.ts updates with related Drizzle config, affected routes/services, and DB handoff documentation before any push or deployment.
  • Migration and production-risk controls: Enforces explicit checks around whether drizzle-kit push is required, which databases are targeted, and blocks high-risk operations (e.g., large UPDATE/DELETE, DROP/TRUNCATE, production migrations) without separate confirmation.
  • Verification workflow: Recommends type checking, migration review, API-call validation, and post-change checks via npm run skills:sync and npm run skills:check.

Quick Start

Review a proposed change by running the office-drizzle-guardian skill for the specific schema/migration update and any related code paths, then confirm whether drizzle-kit push is needed and whether any production-impacting steps were attempted.

Frequently Asked Questions about office-drizzle-guardian

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

FAQPage Schema
How do I safely apply Drizzle schema changes to a Railway PostgreSQL production database?

To safely apply Drizzle schema changes to Railway PostgreSQL, validate related schema files, routes, and handoff documentation before pushing. This workflow blocks risky bulk operations without confirmation and mandates type checking and skills verification.

When should I use drizzle-kit push instead of generating migrations for schema updates?

Deciding when to use drizzle-kit push depends on assessing production data safety and whether the target databases require direct schema synchronization. You must confirm push requirements and review migration plans before executing any schema modifications.

What are the risks of running bulk UPDATE or DELETE operations during a Drizzle migration?

Running bulk UPDATE, DELETE, DROP, or TRUNCATE operations during Drizzle migrations poses severe production data safety risks. These high-risk operations are strictly blocked unless you provide separate, explicit confirmation before execution.

How do I verify Drizzle schema updates and PostgreSQL changes after modifying server/src/db/schema.ts?

Verify Drizzle schema updates by performing type checking, reviewing migrations, and validating API calls. Post-change verification must include running npm run skills:sync and npm run skills:check to ensure consistent application behavior.

Can I run inline npx tsx scripts to test Drizzle queries against a Railway database?

Running inline npx tsx -e scripts to test Drizzle queries against Railway databases is forbidden. You must use script-first guidance under server/scripts to ensure production-safe execution and proper validation.