migration-guidance

Agent Skills › pingdotgg/t3code › migration-guidance

migration-guidance

GitHub

用于指导 v3 到 v4 API 迁移文档的更新，包括处理重命名、移除或变更的符号，验证迁移注解，以及生成和审查参考文档。

.repos/effect-smol/.agents/skills/migration-guidance/SKILL.md pingdotgg/t3code

触发场景

API 从 v3 迁移到 v4 编辑迁移注解重新生成迁移文档

安装

npx skills add pingdotgg/t3code --skill migration-guidance -g -y

更多选项

非标准路径

npx skills add https://github.com/pingdotgg/t3code/tree/main/.repos/effect-smol/.agents/skills/migration-guidance -g -y

不安装直接使用

npx skills use pingdotgg/t3code@migration-guidance

指定 Agent (Claude Code)

npx skills add pingdotgg/t3code --skill migration-guidance -a claude-code -g -y

安装 repo 全部 skill

npx skills add pingdotgg/t3code --all -g -y

预览 repo 内 skill

npx skills add pingdotgg/t3code --list

SKILL.md

Frontmatter

{
    "name": "migration-guidance",
    "description": "Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration\/v3-to-v4.md."
}

Update guidance when a v3 public module or API is renamed, moved, removed, replaced, or gains a materially different v4 contract. A v4-only API without a v3 counterpart does not automatically need an annotation.

Account for every affected v3 symbol.
Read annotations.md before adding or changing annotation YAML. Verify every suggested replacement against implementation and tests.
When checking or regenerating the reference, or when the API change exists in a committed ref, read generation.md. Otherwise report that generation is deferred.
When output was generated, inspect it for unrelated movement and stale refs.

The task is complete when every affected v3 symbol is accounted for, annotation replacements are verified, checks and generation succeed when the change is in a committed ref, and every generated difference is explained. Report deferred checks explicitly for uncommitted API changes.