using-refactoring-catalog-and-code-smells

name	using-refactoring-catalog-and-code-smells
description	Use the refactoring catalog and code smells neurosymbolic module: RAG library, agent brain, growable KB — proof-checked
version	0.1.0

using-refactoring-catalog-and-code-smells

This module is a CULTIVATED, PROOF-CHECKED knowledge organism about refactoring catalog and code smells (183 concepts / 128 relations; grown by a KB factory — every region admitted by a Prolog consistency gate, wrongness tracked as open supersede-issues, never hidden).

The four ways to use it

1. As RAG — the sibling understand-{x} skills in this plugin, coordinate-addressed (call number = home class : dependency facets — the import web, literally); FTS5 index via skilltree.build_index over ${CLAUDE_PLUGIN_ROOT}/skills/using-refactoring-catalog-and-code-smells/references/skilltree.json.
2. As an agent — brain_ask("your question"): the activation graph fires the matching gyri numerically, each answers over its territory, the synthesis is PROVEN one level up (SES tower) and returns with receipts.
3. As tools your agents hold — ee_v2.kbc.heaven_tools.make_kbc_tools over this module's data root (${CLAUDE_PLUGIN_ROOT}/skills/using-refactoring-catalog-and-code-smells/data/): 14 heaven tools (kb_, kernel_, brain_*). Hand them to any heaven agent's tools=[...].
4. As a factory — the kbworld round deepens this module on a schedule; file a kb-door issue to point it somewhere; file kb-supersede when you catch it being wrong (it also catches itself — see the round reports).

The data resources (all inside THIS skill)

• data/concepts.jsonl + data/relations.jsonl — the certified graph
• data/hyperedges.jsonl — the certificate ledger (the automaton's KNOWN)
• data/skeletons.jsonl — certified argument DAGs (because/since/…)
• data/worklist.json — what the module knows it doesn't know
• references/skilltree.json — the library index

Etiquette (the laws this module lives under)

• The prover admits; you never hand-edit certified state (file issues).
• Wrongness is fuel: a wrong-but-coherent region is a PENDING OBSERVATION — say what you saw, the next round metabolizes it.
• The worklist is honest: kb_work shows exactly what the module knows it doesn't know.

The map

• deep_bloaters.lpl
• deep_dispensables.coc_001
• refactoring_catalog_and_code_smells.bloaters
• refactoring_catalog_and_code_smells.primitive_obsession
• refactoring_catalog_and_code_smells.refused_bequest
• refactoring_catalog_and_code_smells.dispensables
• refactoring_catalog_and_code_smells.couplers
• refactoring_catalog_and_code_smells.brain_overload
• refactoring_catalog_and_code_smells.long_method
• refactoring_catalog_and_code_smells.large_class
• refactoring_catalog_and_code_smells.data_clump
• refactoring_catalog_and_code_smells.oop_abusers