interface-migration
Skill177 starsChanged 7 days agoApache-2.0View on GitHub
Evolve Proto, configuration, topic, or Bazel module interfaces across producers and consumers. Use for compatibility changes, deprecations, and coordinated cross-repository migrations.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-evaluationSkill
- algorithm-developmentSkill
- buildSkill
- change-reviewSkill
- container-buildSkill
- engineering-solution-designSkill
- issue-localizationSkill
- lintSkill
- long-horizon-developmentSkill
- model-artifact-integrationSkill
- multi-repo-devSkill
- performance-optimizationSkill
- repository-agent-setupSkill
- simulation-regressionSkill
- test-impact-analysisSkill
- unified-core-runtimeSkill
- vendorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Ask before changing public semantics, published versions, or dependency state outside the approved migration.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interface Migration
Procedure
- Inventory the actual contract, direct producers/consumers, serialized data,
defaults, configuration overlays, and independent checkouts. Read each
affected repository's rules; use
multi-repo-devfor dependency publication. - Specify old/new semantics and error behavior. Check units, frames, time, field presence, enum/default behavior, and persisted-record compatibility where applicable. Do not reuse removed Proto field numbers or names.
- Decide whether coexistence is needed. Prefer an additive migration when independently deployed consumers must overlap; do not add indefinite compatibility layers when an atomic change is sufficient.
- Order provider and consumer changes explicitly. Make unsupported versions fail visibly; define removal and rollback conditions before deletion.
- Validate changed producers and consumers against the same source versions, plus old/new serialized fixtures when compatibility is claimed. Release validation must not be masked by local source overrides.
Acceptance and failure handling
Report achieved compatibility, affected repositories, migration order, evidence, and remaining consumers. Local compilation does not prove deployed compatibility. Ask before changing public semantics, published versions, or dependency state outside the approved migration; do not silently rewrite existing records.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

