Migrate to Shoehorn
SkillFiles & storageThis skill lets your AI migrate existing code to the Shoehorn library. It uses prebuilt engineering steps, so your AI can carry out the migration instead of you working out each change by hand. The steps come straight from the author's own engineering setup.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill, then ask your AI to migrate the code you want moved to Shoehorn. It will follow the prebuilt engineering steps as it works.
Then ask your AI: use the Migrate to Shoehorn skill
What your AI can do with it
- Migrate existing code to the Shoehorn library
- Apply prebuilt engineering steps while migrating
- Hand the migration work to your AI instead of doing it manually
- Use the same skills the author relies on in their own setup
What this skill tells your AI
The instructions your AI receives, as published by asymmetric-al/core in .agents/skills/migrate-to-shoehorn/SKILL.md and read by ahel’s review.
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
asassertions causing problems? - Are they dealing with large objects where only some properties matter?
- Do they need to pass intentionally wrong data for error testing?
- What test files have
-
Install and migrate:
- Install:
npm i @total-typescript/shoehorn - Find test files with
asassertions:grep -r " as [A-Z]" --include="*.test.ts" --include="*.spec.ts" - Replace
as TypewithfromPartial() - Replace
as unknown as TypewithfromAny() - Add imports from
@total-typescript/shoehorn - Run type check to verify
- Install:
Signals
- GitHub stars
- 391
- Forks
- 7
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
migrate-to-shoehorn- Source
- github.com/asymmetric-al/core