fix-angular-fixmes
Installation
SKILL.md
Key rules
- Fix the underlying issue — never just delete the suppression comment and leave broken code.
- Remove the complete comment block: FIXME line (if any) + TODO: Skipped block (if any) + eslint-disable-next-line line.
- Both FIXME-paired and standalone suppressions are the same migration debt.
- For Angular migration rules, prefer CLI schematics over manual edits.
- Do NOT convert service observables to signals (ADR-0027).
- For OnPush and signals patterns, the
angular-modernizationskill is the authoritative source — this skill only owns the ESLint suppression mechanics.
Step 1: Discover all suppressions
Use the Grep tool to find suppressions in the target path:
- Pattern
eslint-disable— finds all eslint suppressions - Pattern
FIXME.*CL-— finds Angular FIXME-tracked ones specifically
Group results by rule name. Two forms appear in this codebase:
Form A — FIXME-paired (a FIXME tracking comment sits above the disable):