mock-updater

Orchestrate parallel subagents to update mock implementations after port interface changes.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jrmatherly/shipit --skill mock-updater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mock-updater
Source: https://github.com/jrmatherly/shipit/tree/main/.claude/skills/mock-updater
Command: npx skills add https://github.com/jrmatherly/shipit --skill mock-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate parallel subagents to update mock implementations when a port interface changes.

Core Features & Use Cases

  • Automates detection of port-interface changes and propagates updates across all mocks in parallel.
  • Supports batch updates via subagents, minimizing merge conflicts and drift.
  • Works across test suites to maintain mock fidelity after interface evolution.

Quick Start

Invoke the mock-updater to synchronize mock implementations after modifying a port interface.

Frequently Asked Questions about mock-updater

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update mock implementations when a port interface changes in TypeScript?

To update mock implementations when a port interface changes, this Skill orchestrates parallel subagents to locate and regenerate all affected mocks across your test suites. It ensures every mock reflects the latest interface without manual search and edit.

What is the best way to fix drifting mocks across multiple unit tests?

The best way to fix drifting mocks is to orchestrate parallel subagents that identify interface changes and batch-adjust all mock implementations. This maintains mock fidelity across your codebase while minimizing merge conflicts.

How do I synchronize mock updates across a large codebase after modifying an interface?

You can synchronize mock updates by running a structured workflow that identifies the interface change, finds all dependent mocks, and generates adjustments in parallel batches. It then verifies consistency using your type systems.

Does this mock update automation work with TypeScript type systems for verification?

Yes, this mock update automation works with TypeScript by verifying mock consistency against your type systems after generating changes. It ensures updated mocks align with the modified port interface before finalizing.

Can I use batch updates to minimize merge conflicts when updating test mocks?

You can use batch updates via parallel subagents to minimize merge conflicts and drift when updating test mocks. This approach propagates interface changes across all mocks simultaneously rather than sequentially.

When should I use parallel subagents for mock updates instead of manual editing?

You should use parallel subagents for mock updates when a port interface change affects multiple unit tests across your codebase. Manual editing risks drift and inconsistency, whereas orchestration ensures all mocks reflect the latest interface.