database-migrations

跨 PostgreSQL、MySQL 及常用 ORM（Prisma、Drizzle、Django、TypeORM、golang-migrate）的模式变更（schema changes）、数据迁移、回滚及零停机部署（zero-downtime deployments）的数据库迁移最佳实践。

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, concise content with strong workflow sequencing and validation for destructive/batch database operations, held back only by a monolithic structure that keeps per-tool detail inline rather than offloading it to reference files.

Suggestions

Split the per-ORM sections (Prisma, Drizzle, Django, golang-migrate) into one-level-deep reference files (e.g. reference/prisma.md) with clearly signaled links from a concise overview, improving progressive disclosure.

Add an explicit 'validate against a production-data copy, then deploy' feedback loop around the batched data-migration SQL so the validate→fix→retry cycle is unmistakable.

Dimension	Reasoning	Score
Conciseness	The body is dense and efficient with no padding — it does not explain concepts Claude already knows; every section (PostgreSQL patterns, per-ORM workflows, expand-contract strategy, anti-patterns table) earns its place with concrete guidance.	3 / 3
Actionability	Fully executable, copy-paste-ready material throughout — real SQL (CREATE INDEX CONCURRENTLY, batched UPDATE with FOR UPDATE SKIP LOCKED), bash commands (prisma migrate deploy, drizzle-kit generate, migrate up), and Django RunPython migration code.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with explicit validation — the Migration Safety Checklist gates execution, the expand-contract pattern has numbered phases with a day-by-day timeline, and golang-migrate 'force VERSION' provides error recovery for dirty state.	3 / 3
Progressive Disclosure	Sections are well organized, but the ~330-line skill is a single monolithic file with five per-ORM sections (Prisma, Drizzle, Django, golang-migrate) inlined that could appropriately be split into one-level-deep reference files; no bundle files exist.	2 / 3
	Total	11 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description naming concrete tools and actions with natural trigger terms, but it lacks an explicit 'Use when...' clause, which caps completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when planning or executing database schema changes, data migrations, rollbacks, or zero-downtime deployments across PostgreSQL/MySQL or ORMs like Prisma, Drizzle, Django, TypeORM, or golang-migrate.'

Consider adding common phrasing variations users might say ('migrate the database', 'add a column to a table', 'backfill data') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and targets — '模式变更（schema changes）、数据迁移、回滚及零停机部署' — across named concrete technologies (PostgreSQL, MySQL, Prisma, Drizzle, Django, TypeORM, golang-migrate).	3 / 3
Completeness	The 'what' is strong (best practices for schema changes, data migration, rollback, zero-downtime across specific tools), but there is no explicit 'Use when...' trigger clause, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered — '数据库迁移', '模式变更/schema changes', '数据迁移', '回滚', '零停机部署/zero-downtime deployments' — the phrases a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	It carves out a clear niche — database migrations for specific DBs/ORMs with named tools — making it unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: skills/database-migrations/SKILL.md
Commit: dfbf946

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.