fec-code-smells

Installation
SKILL.md

Code Smell Diagnosis

Overview

Diagnose structural problems from concrete evidence. A smell is a prompt to investigate, not proof that code must change.

Procedure

  1. Establish the requested scope and project facts.
  2. Collect concrete structural and change-coupling evidence.
  3. Match evidence against the smell catalog.
  4. Apply false-positive checks.
  5. Report confidence, impact, and candidates from the mapping guide.
  6. If the request is diagnosis-only, do not modify business code.

Finding Contract

Every finding states location, evidence, smell ID/name, impact, confidence (HIGH, MEDIUM, LOW), candidate refactorings, priority, and material false-positive considerations. LOW confidence is never an automatic-edit signal.

Installs
1
GitHub Stars
23
First Seen
Oct 28, 2026