Menu

Individual skill

migration-guidance

Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration/v3-to-v4.md.

repos/effect/.agents/skills/migration-guidance/SKILL.md

Read pinned source

Source commit a471adb24d750ab9e8d8312edad53ff6f26d961b

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
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)
1,206
Repository last updated
Nov 7, 2026
License
MIT

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

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.

1. Account for every affected v3 symbol.
2. Read [annotations.md](annotations.md) before adding or changing annotation
   YAML. Verify every suggested replacement against implementation and tests.
3. When checking or regenerating the reference, or when the API change exists in
   a committed ref, read [generation.md](generation.md). Otherwise report that
   generation is deferred.
4. 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