Home/Testing & QA/migrate-to-shoehorn
M

migrate-to-shoehorn

by @mattpocockv
4.9(22)

Replace TypeScript 'as' assertions in test code with type-safe shoehorn patterns, improving test maintainability and type safety.

testingtypescripttype-safetytest-automationcode-qualityGitHub
Installation
npx skills add https://github.com/mattpocock/skills --skill migrate-to-shoehorn
compare_arrows

Before / After Comparison

1 组
Before

Type errors are masked when using 'as' assertions, leading to tests passing but runtime crashes, which are difficult and time-consuming to troubleshoot.

After

Shoehorn provides a type-safe alternative, catching type errors at compile time, making tests more reliable and maintainable.

SKILL.md

migrate-to-shoehorn

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

npm i @total-typescript/shoehorn

Migration patterns

Large objects with few needed properties

Before:

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:

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

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

as Type → fromPartial()

Before:

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

After:

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

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

as unknown as Type → fromAny()

Before:

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

After:

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

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?

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

Weekly Installs279Repositorymattpocock/skillsGitHub Stars4.6KFirst SeenFeb 13, 2026Security AuditsGen Agent Trust HubFailSocketPassSnykPassInstalled onopencode260codex257gemini-cli256github-copilot251kimi-cli250amp250

User Reviews (0)

Write a Review

Effect
Usability
Docs
Compatibility

No reviews yet

Statistics

Installs471.2K
Rating4.9 / 5.0
Version
Updated2026年10月23日
Comparisons1

User Rating

4.9(22)
5
27%
4
55%
3
18%
2
0%
1
0%

Rate this Skill

0.0

Compatible Platforms

🔧Claude Code

Timeline

Created2026年3月20日
Last Updated2026年10月23日
🎁 Agent Knowledge Cards
Survey