mp-suppression-audit

Audits lint suppression and downgrade rules, classifying them as REMOVE, KEEP, or UPGRADE.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits repository-wide code quality suppressions and lint rule downgrades so they don’t quietly weaken your quality gates over time.

Core Features & Use Cases

  • Finds suppression patterns across source and config for ESLint, Fallow, Svelte, TypeScript, Oxlint, and config-level rule changes.
  • Classifies each suppression as REMOVE, KEEP, or UPGRADE based on whether a simple fix exists, whether the suppression is truly required, and whether rules were recently downgraded.
  • Auto-fixes and verifies by removing unjustified suppressions, fixing the underlying code/config issues, running checks, and publishing a PR with the evaluation table for review.
  • Use case: If your repo has grown many eslint-disable comments and config rules set to "off" or 0, run this audit to turn them into actionable fixes and restore consistent lint enforcement.

Quick Start

Tell the AI to run the mp-suppression-audit skill to audit all suppressions, fix the ones that are removable or should be upgraded, and open a PR with an evaluation table.

Frequently Asked Questions about mp-suppression-audit

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

FAQPage Schema
How do I find and remove unjustified eslint-disable comments in my repository?

An eslint-disable suppression audit scans source and config files for ignore patterns and downgraded rules, classifying each as REMOVE, KEEP, or UPGRADE based on whether a simple fix exists to restore consistent lint enforcement.

Can I automatically fix lint rules that are set to off or 0 in my config?

Yes, you can automatically fix lint rules set to off or 0 by upgrading the config, fixing the underlying code issues, running check suites to verify, and creating a PR with an evaluation table for review.

Does this lint suppression audit work with TypeScript, Svelte, and Oxlint ignore patterns?

Yes, the suppression audit supports ESLint, Fallow, Svelte, TypeScript, and Oxlint, scanning both source code and configuration files to identify unjustified disables and recently downgraded rules across these tools.

What is the best way to track and clean up lint rule downgrades in a pull request?

The best way to track lint rule downgrades is to publish a PR containing an evaluation table that classifies each suppression as REMOVE, KEEP, or UPGRADE, ensuring downgraded rules are reviewed and fixed to maintain quality gates.

How do I classify which eslint-disable comments to keep versus remove during a static analysis audit?

Classify eslint-disable comments by evaluating whether a simple fix exists for the underlying issue, whether the suppression is truly required, and whether the rules were recently downgraded to determine REMOVE, KEEP, or UPGRADE status.