database-migration SKILL.md skillA
database-migration from kimyx0207/kim_service is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kimyx0207/kim_service/database-migration@git:20261111.89b2b28Pins git:20261111.89b2b28 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kimyx0207/kim_service
- Path
skills/database-migration/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261111.89b2b28, committed Nov 11, 2026
- Size
- 2,443 bytes
- Repository stars
- 193
- License
- MIT
数据库渐进迁移(database migration expand contract rollback PostgreSQL)。把数据库结构变更拆成兼容扩展、可重跑回填、切换和清理,保留可恢复路径。用于给已有大表加字段并迁移旧数据。;字段改名怎样不影响旧版本?;检查数据库迁移和回滚方案。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 数据库渐进迁移 把数据库结构变更拆成兼容扩展、可重跑回填、切换和清理,保留可恢复路径。 ## 输入与开始方式 - `change`:当前/目标schema、数据库版本和业务不变量。先找受影响入口与写入者。 - `traffic`:表规模、读写模式、消费者版本和部署顺序。缺规模先做小样本演练,估计项写明。 - `recovery`:备份、恢复时间目标、回滚和校验方式。先确认能恢复何种数据,再决定删旧字段时机。 缺少非关键资料时,先给明确假设下的草案或局部结果;资料补齐后只重验受影响部分。授权已覆盖的可逆工作继续,不重复确认。 ## 执行 1. 定位所有读写者与schema约束,确认数据库版本和变更影响。 2. 设计expand阶段让旧新客户端共存,保持旧行为可用。 3. 按稳定主键分批回填并保存进度,更新条件避免覆盖新写入。 4. 检查锁、时延、数据完整及新旧读路径,再切换消费者。 5. 确认旧写入者消失且恢复路径可用后收缩;记录不可逆点和恢复步骤。 按需要读 [专业方法](references/professional-method.md) 和 [完整案例](references/delivery-template.md)。 ## 交付 - `sequence`:扩展到收缩顺序。 - `backfill`:可重跑回填。 - `verification`:锁和数据验证。 - `recoveryPlan`:回退和清理。 ## 检查结果 - 旧新版本共存时先扩展并双读/双写或兼容映射,校验后才删旧。 - 固定分批边界、检查点与幂等规则,核行数及业务值。 - 按实际版本检查锁/耗时/约束,数据检查含空值、冲突和消费者读取。 - 区分代码回滚、数据恢复及不可逆点,满足条件后清理旧路径。 检查方法和证据要求在 [method.json](method.json);参考 [作者正反例](evals/professional-cases.json) 识别实际错误。 ## 需要额外处理的动作 生产DDL和不可逆数据删除按已有授权及恢复条件执行;迁移脚本、兼容代码和隔离演练可继续。
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5ruzjceofyesftis/73e133a58575d5f4a1aab32b64c53f9dbc276ed71072d3edc6048ebfe5c5ddce.json
Then /plugin install database-migration@markdownregistry-5ruzjceofyesftis in Claude Code. It installs git:20261111.89b2b28, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kimyx0207/kim_service/database-migration@sha256:73e133a58575d5f4The line at the top of this page pins the label git:20261111.89b2b28, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5ruzjceofyesftis)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kimyx0207/kim_service/database-migration since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of database-migration from somewhere else? Ask it: where did my database-migration come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 11, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/database-migration/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2443 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kimyx0207/kim_service · 193 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5ruzjceofyesftis GET https://markdownregistry.com/api/v1/resolve?ref=kimyx0207/kim_service/database-migration GET https://markdownregistry.com/api/v1/blob/73e133a58575d5f4a1aab32b64c53f9dbc276ed71072d3edc6048ebfe5c5ddce
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kimyx0207/kim_service
Every file in kimyx0207/kim_service