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

Trigger Scenarios

v3 公共 API 映射变更编辑迁移注释重新生成迁移文档

Install

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

More Options

Non-standard path

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

Use without installing

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.