What problem does it solve?
The Bitwarden clients codebase accumulates eslint-disable suppression comments (often paired with FIXME tickets like CL-764 and CL-903) that hide real technical debt. This Skill removes those suppressions by actually fixing the underlying code issue rather than just deleting the comment.
Core Features & Use Cases
- Suppression Discovery: Uses Grep patterns to find all eslint-disable and FIXME-tracked suppressions, grouped by rule name.
- Rule-Specific Fix Guidance: Provides before/after patterns for Angular rules (OnPush change detection, signals, output emitter refs), TypeScript rules (no-floating-promises, no-unused-vars, no-unsafe-function-type), RxJS rules (no-async-subscribe, prefer-takeuntil), Bitwarden custom rules (no-enums, no-bwi-class-usage), and template/Tailwind rules.
- Validation Workflow: Includes a per-instance cleanup checklist and validation via npm run lint:fix and npm run test.
- Use Case: When asked to "fix FIXMEs" or "clean up eslint-disable-next-line" in a module, the Skill locates each suppression, applies the correct fix (e.g., adding OnPush change detection or converting inputs to signals), removes the full comment block, and verifies lint passes.
Quick Start
Ask the AI to fix the eslint suppressions in a specific directory, for example: "Fix the FIXME eslint suppressions in libs/components using the fix-angular-fixmes skill."