Menu

Individual skill

keep-why-schema-migration

0upvotes

Use when a project context store is read or written, or when its context-schema differs from the installed entry format. Not for remote, publish, deploy, or irreversible changes.

.devin/skills/keep-why-schema-migration/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Keep why schema migration

## Contract

| Field | Bound contract |
|---|---|
| Trigger | A project context store is read or written: compare its recorded `context-schema` with this skill's entry-format version before any store write. If the value is behind or ahead, follow the corresponding migration or blocked path. |
| Authority | The read-only schema comparison may be implicitly invoked; rewriting entry files and the `context-schema` field inside the named project context store requires an explicit operator answer. Every other write is reversible local, with version control as the rollback. Nothing is written outside the store, and nothing is migrated silently. |
| Side effect | Rewrites existing entries per the migration catalog below, marking missing info `undefined` with a reason (never guessed); updates the `context-schema` field only after every entry is caught up. |
| Done | The schema comparison runs every session before the store is written; migrations happen only with explicit consent; a per-developer decline changes nothing in the project store; in the ahead state no entry writes happen until the installed skill is updated. |

## Inputs

- Required: path to the project context store: the directory holding the project's entry files and its config file, which records `context-schema: <version>`.