Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
mxyhi avatar

Migrate To Shoehorn

  • 72 installs
  • 459 repo stars
  • Updated July 31, 2026
  • mxyhi/ok-skills

This is a copy of migrate-to-shoehorn by mattpocock - installs and ranking accrue to the original listing.

Helps with ai & agent building tasks.

About

migrate-to-shoehorn is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • migrate-to-shoehorn
  • AI & Agent Building
  • AI-coding skill

Migrate To Shoehorn by the numbers

  • 72 all-time installs (skills.sh)
  • +4 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mxyhi/ok-skills --skill migrate-to-shoehorn

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs72
repo stars459
Last updatedJuly 31, 2026
Repositorymxyhi/ok-skills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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 TypefromPartial()

Before:

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

After:

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

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

as unknown as TypefromAny()

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

FunctionUse 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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.