Files
dotfiles/modules/claude-code/skills/test-driven-development/refactoring.md
alexion b7363ed7e1 feat(claude-code): manage the user's global config in the Module
Bring the declarative half of ~/.claude into modules/claude-code and apply
it when the Module is enabled: the global agent instructions (context =
./CLAUDE.md), the skills tree (skills = ./skills), the attention-bell hook,
and settings.json (model = opus plus the Stop/Notification/SessionStart
hook wiring).

Runtime state (projects, plugins, cache, history, sessions) and the
.credentials.json secret are left out, so login survives rebuilds and no
secret enters the repo. Verified against the built home-files that
~/.claude/{CLAUDE.md,settings.json,skills,hooks/attention-bell.sh} are
generated, the hook executable.
2026-07-19 07:57:43 -04:00

476 B

Refactor Candidates

After TDD cycle, look for:

  • Duplication → Extract function/class
  • Long methods → Break into private helpers (keep tests on public interface)
  • Shallow modules → Combine or deepen — see DEEPENING.md in /codebase-design for dependency categories and seam discipline
  • Feature envy → Move logic to where data lives
  • Primitive obsession → Introduce value objects
  • Existing code the new code reveals as problematic