skills.rest
spencerbeggs
spencerbeggsCOMMUNITY
Explore all skills by this author →
GitHub

effect-v4-source-lookup

Verify Effect v4 API existence and signatures against vendored source trees.

2|Updated Jul 2, 2026
Search Tags:#typescript#debugging#migration#effect#api-verification#source-lookup
One-click install
npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-source-lookup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: effect-v4-source-lookup
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/effect-v4-source-lookup
Command: npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-source-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ambiguity and memory-based errors that occur when porting or reviewing code against Effect v4, ensuring you rely on actual source-of-truth rather than outdated v3 assumptions.

Core Features & Use Cases

  • Evidence-Based Verification: Provides a structured ladder to verify API renames, existence, signatures, and runtime semantics.
  • Drift Detection: Identifies discrepancies between vendored source trees and installed node_modules to prevent stale lookups.
  • Use Case: When you are unsure if a specific Effect v4 module or function exists or has changed signature, use this skill to perform a controlled probe that validates the API against the exact version currently installed in your environment.

Quick Start

Use the effect-v4-source-lookup skill to verify the signature and existence of the Effect.catchAll function within your current package.

Frequently Asked Questions about effect-v4-source-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Effect v4 API signatures during a TypeScript migration?▼

Verify Effect v4 API signatures by cross-referencing vendored source trees and installed node_modules. This controlled probe validates API existence, signatures, and runtime semantics against the exact version currently installed, preventing stale v3 assumptions.

What is the best way to check for Effect v3 to v4 API drift?▼

Check for Effect v3 to v4 API drift by identifying discrepancies between vendored source trees and installed node_modules. This version-gated source resolution detects module renames and signature changes to prevent runtime instability.

Why does my Effect v4 code fail with runtime instability after migration?▼

Runtime instability during migration usually stems from memory-based errors and outdated v3 assumptions. Relying on source-of-truth verification instead of memory ensures you use actual Effect v4 module semantics and signatures.

Does this Effect v4 source lookup work with my installed TypeScript environment?▼

Effect v4 source lookup works within your current TypeScript environment by applying shell-based probing to resolve exact installed versions. It requires precise version-gated source resolution to confirm non-stale APIs accurately.

How do I validate Effect v4 module existence without relying on outdated documentation?▼

Validate Effect v4 module existence using evidence-based verification against vendored source trees. This structured ladder confirms API renames and existence directly from the installed package, eliminating reliance on outdated v3 documentation.

Related Skills

Explore More Software Engineering Skills→
soyasissoyasis

gstack-upgrade

Upgrade gstack across global, local, and vendored installs with rollback.

Community
Advanced
ys0714ys0714

qa-tester

Run Vitest and TypeScript test suites with failure diagnosis and repair attempts.

Community
Advanced
zeronx798zeronx798

claude-code

Delegate software development tasks to the Claude Code CLI for file manipulation, code review, and shell commands.

Community
Advanced
eboodyeboody

animejs

Provide API reference and version-specific guidance for the anime.js JavaScript library.

Community
Basic