review-static-lintignore

Audit lint-ignore suppressions in PowerShell and AutoHotkey files.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-static-lintignore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-static-lintignore
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/review-static-lintignore
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-static-lintignore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the potential overuse and misuse of lint-ignore comments, ensuring that static analysis checks are not being bypassed inappropriately, which could lead to undetected issues.

Core Features & Use Cases

  • Comprehensive Audit: Scans all lint-ignore suppressions within the codebase.
  • Detailed Analysis: Evaluates the appropriateness of each suppression tag and its individual usage sites.
  • Use Case: A developer can use this Skill to systematically review all instances where static analysis checks have been suppressed, identifying any that are no longer necessary or that mask genuine problems.

Quick Start

Audit every lint-ignore suppression in the codebase for appropriateness and overuse.

Frequently Asked Questions about review-static-lintignore

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

FAQPage Schema
How do I audit lint-ignore suppressions across my codebase?

To audit lint-ignore suppressions, this Skill scans all usage sites and check definitions, evaluating each suppression for appropriateness. It identifies legitimate exceptions, workarounds, stale suppressions, and areas where static analysis checks need improvement.

Why should I review static analysis suppression comments in my source files?

Reviewing static analysis suppression comments is necessary because overusing lint-ignore directives can mask genuine problems. Auditing them ensures checks are not bypassed inappropriately, preventing undetected issues from accumulating in the codebase.

What's the best way to find stale lint-ignore comments in PowerShell and AutoHotkey scripts?

The best way to find stale lint-ignore comments is running a comprehensive suppression audit that analyzes PowerShell check scripts and AutoHotkey source files. This process flags suppressions that are no longer necessary or mask genuine problems.

Does this lint suppression audit work with AutoHotkey source files and PowerShell scripts?

Yes, the lint suppression audit works with AutoHotkey source files and PowerShell scripts. It requires analyzing both the PowerShell check scripts and the AutoHotkey source files to evaluate suppression tag definitions and usage sites.

Can I identify which lint-ignore suppressions are legitimate exceptions versus unnecessary workarounds?

Yes, you can identify legitimate exceptions versus unnecessary workarounds by evaluating both check definitions and usage sites. The audit categorizes suppressions into legitimate exceptions, workarounds, stale suppressions, and areas for check improvement.

When should I not use lint-ignore comments to suppress static analysis warnings?

You should not use lint-ignore comments when they mask genuine problems or bypass static analysis checks inappropriately. The audit identifies these overused suppressions and highlights areas for check improvement instead of suppression.