Reek Skill

Overview

Treat Reek warnings as design feedback, not formatting noise. A smell usually points to an object boundary, responsibility, or API problem. Prefer fixing the underlying design issue over suppressing the detector.

Workflow

1. Read the smell name and the flagged method or class.
2. Identify the design pressure:
   • too many responsibilities
   • caller-controlled branching
   • missing abstraction
   • behavior living on the wrong object
   • hidden state or implicit setup
3. Fix the smallest real design problem.
4. Re-run Reek on the changed files using reek . (always pass the explicit directory argument — bare reek defaults to scanning . only when stdin is a TTY, which is not the case in agent runners or CI).
5. If the warning appears to conflict with an intentional framework pattern, stop and check project-local guidance before changing code or suppressing the smell.