Skip to main content
skill Claude Code

migrate-to-shoehorn — Claude Code skill: test migration

Replaces as type assertions in tests with helpers from @total-typescript/shoehorn. Use it when tests need partial objects or deliberately invalid data.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add mattpocock/skills
/plugin install mattpocock-skills@mattpocock
Open on GitHub

What migrate-to-shoehorn does

The skill finds as assertions in test files and moves them to Shoehorn helpers. It replaces as Type with fromPartial(), so a test can pass only the fields it needs.

For deliberately incorrect values, it uses fromAny(). The migration adds imports from @total-typescript/shoehorn and calls for a type check afterwards. fromExact() is available when a test must start with a full object before switching to fromPartial().

Shoehorn belongs in test code only. Install this skill if your tests are full of mocked fields or as unknown as Type casts; skip it for production code.

What it helps with

  • replace as Type with fromPartial() in tests
  • pass selected fields from a large object
  • test invalid input with fromAny()
  • find assertions in *.test.ts and *.spec.ts files
  • add @total-typescript/shoehorn imports

Example prompts for the agent

  • “Find `as Request` in the tests and migrate it to shoehorn.”
  • “Replace `as unknown as Type` in `*.spec.ts` with `fromAny()`.”
  • “I need to pass a partial Request in a test without filling every field.”

How to install migrate-to-shoehorn

1Plugin marketplace

/plugin marketplace add mattpocock/skills
/plugin install mattpocock-skills@mattpocock

This installs the whole mattpocock-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add mattpocock/skills --skill migrate-to-shoehorn -a claude-code

3Manually: put the files in place

~/.claude/skills/migrate-to-shoehorn/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/migrate-to-shoehorn/

From the same set32

The whole set →
grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. Claude Code 1,163,035installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. Claude Code 1,141,062installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. Claude Code 1,038,491installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. Claude Code 990,453installs prototype Matt Pocock Creates throwaway prototypes for checking state logic or exploring UI before committing the decision to the main codebase. Claude Code 986,201installs

Similar

webapp-testing official anthropics This skill tests local web apps with Playwright, helping agents debug UI behavior, capture screenshots, and inspect browser logs. Claude Code Claude.ai 186,758installs systematic-debugging Jesse Vincent Makes the agent investigate the cause of a failure before it suggests a patch. Use it for failing tests, build errors, and behaviour that does not match expectations. Claude Code CX Codex 306,118installs requesting-code-review Jesse Vincent Sends completed work to a reviewer subagent after a task, major feature, or before merging to main. It keeps the review focused on the change and its requirements. Claude Code CX Codex 262,135installs test-driven-development Jesse Vincent This skill guides an agent through test-first development: verify a test fails, write the smallest passing change, then refactor. It covers features, bug fixes, and behavior changes. Claude Code CX Codex 259,292installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. Claude Code CX Codex Cursor +1 673,100installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. Claude Code Claude.ai 414,180installs agent-browser vercel-labs A CLI skill for browser control: it opens pages, fills forms, clicks buttons, and tests web apps. Use it when an agent needs to act inside a website. Claude Code CX Codex Cursor +1 1,200,000installs

Questions about migrate-to-shoehorn

How do I install migrate-to-shoehorn in Claude Code?

Add the skill with npx skills add mattpocock/skills --skill migrate-to-shoehorn -a claude-code.

What does migrate-to-shoehorn do?

It migrates test type assertions written with as to helpers from @total-typescript/shoehorn. The skill separates partial test data from deliberately invalid values.

When should I use fromPartial(), fromAny(), or fromExact()?

Use fromPartial() for incomplete data that still type-checks. Use fromAny() for intentionally wrong test input, while fromExact() requires a full object.

Source text

SKILL.md · MIT
---
name: migrate-to-shoehorn
description: Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
---

# Migrate to Shoehorn

## Why shoehorn?

`shoehorn` lets you pass partial data in tests while keeping TypeScript happy. It replaces `as` assertions with type-safe alternatives.

**Test code only.** Never use shoehorn in production code.

Problems with `as` in tests:

- Trained not to use it
- Must manually specify target type
- Double-as (`as unknown as Type`) for intentionally wrong data

## Install

```bash
npm i @total-typescript/shoehorn
```

## Migration patterns

### Large objects with few needed properties

Before:

```ts
type Request = {
  body: { id: string };
  headers: Record<string, string>;
  cookies: Record<string, string>;
  // ...20 more properties
};

it("gets user by id", () => {
  // Only care about body.id but must fake entire Request
  getUser({
    body: { id: "123" },
    headers: {},
    cookies: {},
    // ...fake all 20 properties
  });
});
```

After:

```ts
import { fromPartial } from "@total-typescript/shoehorn";

it("gets user by id", () => {
  getUser(
    fromPartial({
      body: { id: "123" },
    }),
  );
});
```

### `as Type` → `fromPartial()`

Before:

```ts
getUser({ body: { id: "123" } } as Request);
```

After:

```ts
import { fromPartial } from "@total-typescript/shoehorn";

getUser(fromPartial({ body: { id: "123" } }));
```

### `as unknown as Type` → `fromAny()`

Before:

```ts
getUser({ body: { id: 123 } } as unknown as Request); // wrong type on purpose
```

After:

```ts
import { fromAny } from "@total-typescript/shoehorn";

getUser(fromAny({ body: { id: 123 } }));
```

## When to use each

| Function        | Use case                                           |
| --------------- | -------------------------------------------------- |
| `fromPartial()` | Pass partial data that still type-checks           |
| `fromAny()`     | Pass intentionally wrong data (keeps autocomplete) |
| `fromExact()`   | Force full object (swap with fromPartial later)    |

## Workflow

1. **Gather requirements** - ask user:
   - What test files have `as` assertions causing problems?
   - Are they dealing with large objects where only some properties matter?
   - Do they need to pass intentionally wrong data for error testing?

2. **Install and migrate**:
   - [ ] Install: `npm i @total-typescript/shoehorn`
   - [ ] Find test files with `as` assertions: `grep -r " as [A-Z]" --include="*.test.ts" --include="*.spec.ts"`
   - [ ] Replace `as Type` with `fromPartial()`
   - [ ] Replace `as unknown as Type` with `fromAny()`
   - [ ] Add imports from `@total-typescript/shoehorn`
   - [ ] Run type check to verify

© Matt Pocock · MIT · mattpocock/skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor