Agent Skills
› sediman-agent/OpenSkynet
› principle-migrate-callers-then-delete-legacy-apis
principle-migrate-callers-then-delete-legacy-apis
GitHub指导在引入新内部API时，同步迁移调用方并删除旧接口，避免保留兼容性层。适用于无外部依赖、可承受破坏性变更且旨在简化代码库的重构场景，以减少双路径复杂度。
Trigger Scenarios
引入新的内部API设计
清理遗留的内部API接口
执行代码库简化重构
Install
npx skills add sediman-agent/OpenSkynet --skill principle-migrate-callers-then-delete-legacy-apis -g -y
SKILL.md
Frontmatter
{
"name": "principle-migrate-callers-then-delete-legacy-apis",
"description": "Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.",
"disable-model-invocation": true
}
Migrate Callers Then Delete Legacy APIs
When we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving compatibility layers.
Rule:
- Do not keep legacy API paths alive only because internal callers still exist
- Inventory callers, migrate them, and delete the old API immediately
- Treat temporary adapters as exceptional and time-boxed, not default architecture
- Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details
When this applies:
- No external users depend on backward compatibility
- The project can absorb coordinated breaking changes
- The new API is part of a simplification or refactor initiative
Keeping both old and new APIs creates dual-path complexity, slows cleanup, and makes the codebase feel append-only.
Version History
- c9d8953 Current 2026-07-05 19:53
