mp-check-fix

Detect and run Node/TypeScript check scripts, then iteratively fix failing commands.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-check-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-check-fix
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/skills/mp-check-fix
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-check-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates slow, inconsistent development cycles by deterministically detecting the right project check scripts and running a structured check-to-fix loop until failures are resolved.

Core Features & Use Cases

  • Deterministic check detection: Inspects package.json (including common monorepo workspace layouts) to discover available check scripts and the correct package manager.
  • Predictable execution plan: Runs CHECK_ALL (then BUILD) when available, otherwise runs TYPECHECK → LINT → FORMAT → BUILD in a fixed order.
  • Targeted fix loop: Parses failures, inspects relevant files, attempts minimal changes guided by root cause (with a TDD-first bias when feasible), and retries up to three iterations per failing command.

Use case: You want an AI to reliably run the correct TypeScript/build/lint/format checks for your repo, fix what it can, and leave you with a clear pass/fail summary instead of ad-hoc commands and guessing script names.

Quick Start

Run mp-check-fix in your project directory to have it detect available check scripts and iteratively fix any failures before summarizing results.

Frequently Asked Questions about mp-check-fix

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

FAQPage Schema
How do I automatically fix lint and typecheck errors in a TypeScript monorepo?

To automatically fix lint and typecheck errors in a TypeScript monorepo, run this Skill to detect available package scripts and iteratively apply minimal fixes to failing commands. It parses failures, inspects relevant files, and retries up to three times per command.

What is the execution order for running build and check scripts in a Node project?

The execution order for running check scripts prioritizes a CHECK_ALL command if available, otherwise it strictly runs TYPECHECK, then LINT, then FORMAT, and finally BUILD to validate your Node project deterministically.

Can I use this to run check scripts for basic monorepo workspace layouts?

Yes, you can run check scripts for basic monorepo workspace layouts. It inspects package.json files to discover available scripts, supports monorepo-prefixed scopes, and correctly identifies the package manager before execution.

How does the automated fix loop handle failing build validation commands?

The automated fix loop handles failing build validation commands by parsing the failure output, inspecting relevant files, and attempting minimal changes guided by the root cause, retrying the command up to three iterations.

What are the limitations of using an automated check-to-fix loop for project maintenance?

A limitation of the automated check-to-fix loop is that it caps fix attempts at three iterations per failing command, meaning complex or deeply rooted build validation issues may remain unresolved and require manual intervention.