Skip to content
Back to skills

Quality Eslint Eslint Disable Governance

ASecurity

Governs eslint-disable usage by classifying justified versus unjustified suppressions, requiring technical justification, and cleaning up unnecessary rule disables without changing behavior.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
developmentjavascripttypescriptgojavanodegit

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill quality--eslint--eslint-disable-governance --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quality Eslint Eslint Disable Governance?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Quality  Eslint  Eslint Disable Governance
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-quality-eslint-eslint-disable-governance/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-quality-eslint-eslint-disable-governance)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: quality.eslint.eslint-disable-governance
name: ESLint Disable Governance
description: >
  Governs eslint-disable usage by classifying justified versus unjustified suppressions, requiring technical justification, and cleaning up unnecessary rule disables without changing behavior.
stack:
  - JavaScript
  - TypeScript
category: eslint
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - eslint disable governance
  - eslint-disable
  - ts-ignore
  - ts-expect-error
  - lint suppression
  - disable comments
compatibility:
  runtime:
    browser: true
    node: true
---

# ESLint Disable Governance

## Purpose

Use this skill to control `eslint-disable` and similar suppressions.

Suppressions are debt. They may be justified, but they must be visible, explained, and periodically re-evaluated.

The core rule is simple:

```txt
Every suppression needs a reason and an expiry path.
```

## When to Use

Use this skill when:

- the repo has many lint suppressions
- `eslint-disable` is hiding debt
- `ts-ignore` or `ts-expect-error` needs triage
- a cleanup pass is needed before harder lint rules

## Do

Locate:

- `eslint-disable`
- `eslint-disable-next-line`
- `ts-ignore`
- `ts-expect-error`

Classify each suppression:

- justified
- temporary
- unnecessary
- suspicious

Require a technical reason for keeping it.

## Do Not

Avoid removing suppressions blindly when they protect a known issue.

Avoid allowing suppressions with no comment or ticket path when governance expects one.

Avoid changing behavior accidentally while removing a disable.

## Review Checklist

- [ ] Suppressions are found and classified.
- [ ] Justifications are technical, not cosmetic.
- [ ] Unnecessary suppressions are removed.
- [ ] Behavior is preserved.

## Expected Output

1. Inventory suppressions.
2. Classify their legitimacy.
3. Remove unnecessary disables.
4. Preserve behavior.
5. Record remaining suppressions clearly.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…