mp-fallow-fix

Diagnose fallow dead-code findings and apply removals or justified suppressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It diagnoses and resolves fallow dead-code regressions and audit failures so your codebase passes quality checks without losing intentional functionality.

Core Features & Use Cases

  • Dead-code failure triage: Classifies issues from fallow output into fix vs suppress actions, including unused exports/types, stale suppressions, and audit-blocking findings.
  • Targeted remediation with baselines: Re-runs the failing fallow checks, and updates the dead-code baseline when the change is legitimate.
  • Suppression hygiene: Applies specific suppression kinds only when justified, ensuring stale or orphaned suppressions (with stale-suppressions set to error) don’t break CI.

Quick Start

Diagnose and fix fallow failures by instructing the AI to run the appropriate fallow diagnostics, apply removals or justified suppressions, update the baseline if needed, and verify that check:fallow and fallow:audit both pass.

Frequently Asked Questions about mp-fallow-fix

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

FAQPage Schema
How do I fix fallow dead-code regressions blocking my push?

Fix fallow dead-code regressions by parsing JSON issue outputs to classify findings, applying targeted code removals or justified suppression annotations, and re-running pnpm checks to verify the fix.

What is the best way to handle unused exports reported by a fallow audit?

Handle unused exports reported by a fallow audit by diagnosing the rule-level findings, removing the dead code if it is truly unnecessary, or applying justified suppression annotations if the export is intentionally retained.

Why do stale fallow suppressions break CI and how do I resolve them?

Stale fallow suppressions break CI when stale-suppressions are set to error, requiring you to remove orphaned suppressions or update them with specific suppression kinds to pass the fallow audit.

How do I update a pnpm fallow baseline when the dead-code count changes?

Update a pnpm fallow baseline by running pnpm fallow:save-baseline after verifying that the dead-code count change is legitimate and check:fallow passes.

Can I use specific suppression kinds to ignore fallow audit failures?

You can use specific suppression kinds like @public or fallow-ignore to suppress fallow audit failures, applying them only when justified to maintain suppression hygiene and prevent CI blocks.

What should I do when check:fallow fails but the dead-code is intentional?

When check:fallow fails due to intentional dead-code, apply justified suppression annotations to the specific findings, then re-run the fallow checks to confirm both check:fallow and fallow:audit pass.