MI

migrate-to-shoehorn

Refactor TypeScript 'as' assertions in tests to use @total-typescript/shoehorn helpers.

Install

mkdir -p .claude/skills/migrate-to-shoehorn-jupes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16476" && unzip -o skill.zip -d .claude/skills/migrate-to-shoehorn-jupes && rm skill.zip

Installs to .claude/skills/migrate-to-shoehorn-jupes

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Migrate test files from `as` assertions to @total-typescript/shoehorn helpers. Use when tests need partial fixtures, intentionally invalid data, or safer replacements for TypeScript assertions.
193 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • →Migrate test files from `as` assertions to `@total-typescript/shoehorn` helpers
  • →Replace `value as Type` with `fromPartial(value)` for partial fixtures
  • →Replace `value as unknown as Type` with `fromAny(value)` for intentionally invalid data
  • →Use `fromExact(value)` for full-shape fixtures during migration
  • →Install `@total-typescript/shoehorn` using the repository's package manager

How it works

This skill identifies `as` assertions in test files and replaces them with `@total-typescript/shoehorn` helpers like `fromPartial()`, `fromAny()`, or `fromExact()`, based on the assertion's intent. It also handles package installation.

Inputs & outputs

You give it
Test files containing TypeScript `as` assertions
You get back
Test files with `as` assertions replaced by `@total-typescript/shoehorn` helpers, and `@total-typescript/shoehorn` installed if needed

When to use migrate-to-shoehorn

  • →Refactor large test objects
  • →Replace 'as unknown as Type' casts
  • →Clean up test fixtures

About this skill

migrate-to-shoehorn

Use this skill to migrate test code only from TypeScript as assertions to @total-typescript/shoehorn helpers.

Shoehorn is for tests, fixtures, and test-only helpers. Do not recommend it for production or source files, and do not add @total-typescript/shoehorn imports outside *.test.* or *.spec.* files.

Install

Install Shoehorn only when the target repository does not already depend on it, and use the package manager already used by that repository:

# bun.lock or bun.lockb
bun add -d @total-typescript/shoehorn

# pnpm-lock.yaml
pnpm add -D @total-typescript/shoehorn

# yarn.lock
yarn add -D @total-typescript/shoehorn

# package-lock.json or npm-shrinkwrap.json
npm install --save-dev @total-typescript/shoehorn

Do not switch package managers. If multiple lockfiles exist, ask which package manager owns the repo before installing.

Find Candidate Tests

Search only test files and review every result manually:

rg "\bas\s+[A-Z][A-Za-z0-9_$]*(<[^>]+>)?" --glob "*.{test,spec}.{ts,tsx}"
rg "\bas\s+unknown\s+as\s+" --glob "*.{test,spec}.{ts,tsx}"

Avoid broad replacements. Migrate one assertion at a time so the new helper matches the test intent.

Before choosing a helper, read migration patterns. Check the installed package declarations for supported exports.

Workflow

  1. Confirm the target files are tests (*.test.ts, *.test.tsx, *.spec.ts, or *.spec.tsx).
  2. Check whether @total-typescript/shoehorn is already installed.
  3. If installation is needed, use the existing package manager from the repo lockfile.
  4. Search for candidate assertions with the rg commands above.
  5. Replace value as Type with fromPartial(value) when the supplied data is partial but type-valid.
  6. Replace value as unknown as Type with fromAny(value) when the supplied data is intentionally invalid.
  7. Use fromExact() only for full-shape fixtures or short-lived migration steps.
  8. Add the narrowest import needed from @total-typescript/shoehorn.
  9. Run the target test file, the repo test suite, and the typecheck command.

Validation

After migrating, run the repository's normal checks. For a Bun-based repo, use:

bun run typecheck
bun test

Verify Shoehorn remains test-only:

rg "@total-typescript/shoehorn"
rg "@total-typescript/shoehorn" --glob "!*.{test,spec}.{ts,tsx}"

The first command should show only intended test imports. The second command should return no source-file imports; if it finds any, remove Shoehorn from production/source code and fix the underlying type boundary instead.

When not to use it

  • →Loosening production typing
  • →Assertions in source code (non-test files)
  • →When the assertion is not in `*.test.*` or `*.spec.*` files

Limitations

  • →Use this skill to migrate test code only.
  • →Do not recommend `@total-typescript/shoehorn` for production or source files.
  • →Avoid broad replacements; migrate one assertion at a time.

How it compares

This skill automates the refactoring of TypeScript `as` assertions in test code to specialized helpers, improving type safety and readability in tests, unlike manual refactoring or general type-checking tools.

Compared to similar skills

migrate-to-shoehorn side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
migrate-to-shoehorn (this skill)06moReviewIntermediate
tdd-workflow67moReviewIntermediate
migrate18moReviewIntermediate
agent-implementer-sparc-coder19moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry