Skip to content
Back to skills

Quality Eslint Eslint Autofix Safe Cleanup Browser V18

ASecurity

Applies safe ESLint autofix cleanup in browser-oriented projects where mechanical fixes must preserve UI behavior, build output, and user-facing runtime contracts.

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

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill quality--eslint--eslint-autofix-safe-cleanup-browser-v18 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quality Eslint Eslint Autofix Safe Cleanup Browser V18?

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

Security grade badge for Quality  Eslint  Eslint Autofix Safe Cleanup Browser V18
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-quality-eslint-eslint-autofix-safe-cleanup-browser/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-quality-eslint-eslint-autofix-safe-cleanup-browser)

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-autofix-safe-cleanup-browser-v18
name: ESLint Autofix Safe Cleanup Browser v18+
description: >
  Applies safe ESLint autofix cleanup in browser-oriented projects where mechanical fixes must preserve UI behavior, build output, and user-facing runtime contracts.
stack:
  - JavaScript
  - TypeScript
category: eslint
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - eslint autofix browser
  - browser lint fix
  - safe autofix browser
  - mechanical fix browser
compatibility:
  runtime:
    browser: true
---

# ESLint Autofix Safe Cleanup Browser v18+

## Purpose

Use this skill for browser-oriented projects where ESLint autofix must preserve UI behavior.

This variant keeps the cleanup mechanical and ensures no DOM, rendering, or user interaction behavior changes slip in through a lint pass.

## When to Use

Use this skill when:

- the runtime is browser-based
- autofix touches UI code
- behavior must stay unchanged
- the cleanup should remain small and reviewable

## Do

Keep browser behavior intact.

Review the diff before accepting it.

Validate rendering or interaction tests when relevant.

## Do Not

Avoid broad autofix changes that alter UI behavior.

Avoid mixing browser behavior changes with lint cleanup.

## Review Checklist

- [ ] Browser behavior is unchanged.
- [ ] The fix is mechanical.
- [ ] The diff is bounded.

## Expected Output

1. Decide whether autofix is safe in browser code.
2. Apply only mechanical changes.
3. Preserve UI behavior.
4. Validate relevant tests.
5. Keep the cleanup bounded.

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…