Skip to content

try-works/role-model / .agents/skills/effect-v3-to-v4

effect-v3-to-v4

Verified

Use this skill when migrating a codebase from Effect v3 to Effect v4, upgrading `effect` or any `@effect/*` package across the v3/v4 boundary.

FileKindSize
PROVENANCE.mdmarkdown1.2 KB
SKILL.mdskill md7.7 KB

PROVENANCE.md

View on GitHub
# Installed skill provenance: `effect-v3-to-v4`

This skill is an installed copy of upstream `Effect-TS/skills`, not first-party text.

| field | value |
| --- | --- |
| upstream | https://github.com/effect-ts/skills |
| path upstream | `skills/effect-v3-to-v4/SKILL.md` |
| commit | `2309e6f27d9955b434c0e3f394b945c136e89fd2` ("Update effect-ts skill to install effect@rc (#12)") |
| retrieved | 2026-09-27 |
| sha256 | `62ef89aa2967b68fab2a29bbb5b8f038ed9e40c047cf8bc08c37d29ba5f48563` |

## Why it is installed here

The public repository's Effect code is on the v4 line (`effect@4.0.0-rc.117`, vendored under `vendor/effect`), and
parts of the router still carry v3 idioms. This skill is the bounded migration workflow for moving a file, package or
module from v3 to v4 against the generated `migration/v3-to-v4.md` reference, so a migration is a planned change
rather than an opportunistic rewrite.

## Refreshing the pin

```bash
git clone --depth 1 https://github.com/effect-ts/skills.git /tmp/effect-skills
cp /tmp/effect-skills/skills/effect-v3-to-v4/SKILL.md .agents/skills/effect-v3-to-v4/SKILL.md
```

Then update this file's commit, retrieval date and digest in the same commit.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall