fix-extreme

Fix blocking type-check, lint, and formatting errors across monorepos with parallel agents.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Ankurjain1121/dev-workflow-skills --skill fix-extreme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-extreme
Source: https://github.com/Ankurjain1121/dev-workflow-skills/tree/main/plugins/fix-extreme
Command: npx skills add https://github.com/Ankurjain1121/dev-workflow-skills --skill fix-extreme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces fast, build-focused code quality by fixing only blocking errors with parallel agents.

Core Features & Use Cases

  • Concurrently targets blocking issues detected by type-check, lint, and formatting tools across monorepos (Turbo, Nx, pnpm).
  • Uses affected-only scanning to minimize work in large repos and PRs.
  • Orchestrates specialized agents (Type Fixer, Lint Fixer, Format Fixer, Import Fixer, Security Fixer) to apply safe, deterministic changes.

Quick Start

Run fix-extreme on your repo to start the blocking-error remediation workflow, and review per-file results in the output logs.

Frequently Asked Questions about fix-extreme

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

FAQPage Schema
How do I fix blocking type-check and lint errors across a monorepo?

To fix blocking type-check and lint errors across a monorepo, this Skill uses parallel agents to apply safe, deterministic changes concurrently across affected packages.

What is affected-only scanning for code quality in large repositories?

Affected-only scanning is a process that minimizes work in large repos and PRs by running type-checking, linting, and formatting exclusively on changed packages rather than the entire codebase.

Does this blocking error fixer work with Turbo, Nx, and pnpm monorepos?

Yes, this blocking error fixer works with Turbo, Nx, and pnpm monorepos, using their native monorepo awareness to scale incremental runs and target affected packages efficiently.

How do I run incremental type-checking and formatting checks on a pull request?

You can run incremental type-checking and formatting checks on a pull request by executing the Skill, which uses affected-only scanning to orchestrate specialized fixers on changed files only.

What is the best way to automate code quality fixes for build-blocking errors?

The best way to automate code quality fixes for build-blocking errors is using a zero-tolerance approach that orchestrates Type, Lint, Format, Import, and Security fixers in parallel to apply deterministic changes.

Why does fix-extreme only target blocking errors instead of all code quality issues?

fix-extreme targets only blocking errors to enforce fast, build-focused code quality, avoiding the overhead of non-blocking warnings while ensuring builds pass quickly in large repositories.