From grimoire
Diagnoses illuminated check engine lights using OBD-II codes, freeze-frame data, and symptom correlation to assess severity and recommend next steps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:diagnose-check-engine-lightThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematically identify the cause of an illuminated check engine light using OBD-II codes and symptom correlation to determine urgency and repair path.
Systematically identify the cause of an illuminated check engine light using OBD-II codes and symptom correlation to determine urgency and repair path.
Adopted by: All US vehicles 1996+ (mandated by EPA OBD-II regulations), ASE-certified technicians, NHTSA emissions compliance programs, AAA diagnostic service network
Impact: OBD-II standardization (SAE J1979) enables diagnosis in minutes vs. hours of manual testing; correct code interpretation prevents $200–$1,500 in unnecessary part replacements; misdiagnosed CEL causes 35% of failed emissions tests (EPA data)
Why best: The SAE J1979 standard ensures any compliant scanner reads all 10,000+ standardized DTCs from any manufacturer; systematic correlation of code + symptoms + freeze-frame data eliminates guessing
Sources: SAE J1979 "E/E Diagnostic Test Modes" standard; NHTSA OBD-II enforcement; ASE "Automobile Test A6 (Electrical/Electronic Systems)" and "A8 (Engine Performance)" certification curricula
Assess light behavior — Steady light: non-critical, engine likely still driveable; flashing/blinking light: active misfire causing catalytic converter damage — stop driving, tow to shop.
Note symptoms — Before scanning, record: any rough idle, power loss, unusual smells, noises, fuel smell, smoke color; symptoms narrow diagnosis before the code is read.
Connect OBD-II scanner — Plug scanner into DLC (Data Link Connector) under the dash, driver's side; turn key to ON (not start) or start engine per scanner instructions; for Bluetooth scanners, pair to app first.
Read all stored DTCs — Retrieve all pending, current, and historical codes; a pending code (P0xxx with "pending" flag) has triggered once but not yet confirmed; record every code number.
Decode each DTC — First digit: P=powertrain, B=body, C=chassis, U=network. Second digit: 0=generic SAE, 1=manufacturer-specific. Third digit: system (1=fuel/air, 2=injector, 3=ignition, 4=emission, 5=speed/idle, 6=output, 7/8=transmission). Decode using scanner database or NHTSA lookup.
Read freeze-frame data — Freeze frame captures engine parameters at the moment the fault set: RPM, coolant temp, fuel trim, load, MAP/MAF reading; this context identifies conditions that triggered the fault.
Prioritize by severity — Critical (stop driving): P0335 (crankshaft sensor), P0017 (cam/crank correlation), P0300-series misfires (flashing CEL). Moderate (repair soon, 1–7 days): P0420 (cat efficiency), P0171/P0174 (lean condition), P0440-series (EVAP). Minor (schedule at next service): P0128 (thermostat), P0446 (EVAP vent).
Verify with live data — Run live data stream for the suspect system: for O2 sensor codes, watch upstream/downstream O2 switching patterns; for fuel trim codes, watch STFT and LTFT at idle and cruise; deviations confirm the fault vs. sensor noise.
Perform basic visual inspection — Check: fuel cap seated and sealed (30% of EVAP codes are loose caps), obvious vacuum hose cracks, oil cap off, air filter housing open, coolant level, obvious wiring damage near heat sources.
Decide repair path — DIY-appropriate: gas cap, air filter, O2 sensor (most vehicles), mass airflow sensor, PCV valve. Shop-required: catalytic converter, transmission codes, internal engine, ABS/SRS (safety systems). Clear codes only after repair; re-drive 50–100 miles to confirm readiness monitors complete.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireDiagnoses brake system faults from symptoms like noise, pulsation, pulling, soft pedal, or warning lights to determine urgency and root cause before driving or seeking repair.
Enforces systematic root cause analysis for bugs, test failures, unexpected behavior, and regressions via five-phase workflow: Understand, Reproduce, Isolate, Fix, Verify.
Diagnoses failures, fixes bugs, and investigates failing tests using systematic debugging: reproduce first, read before changing, assume nothing, find root cause.