dry-business-knowledge
Installation
SKILL.md
Activation Contract
Load this skill when reviewing refactor plans for: DRY, duplicated business knowledge, duplication.
Hard Rules
- Prioritize duplicated rules, validations, formulas, permissions, mappings, or invariants.
- Do not merge coincidentally similar code with different meanings.
- State the business knowledge that would become single-sourced.
- Preserve observable behavior; label functional changes as follow-up.
- Require evidence for every recommendation, or mark it as a hypothesis.
Decision Gates
| Signal | Action |
|---|---|
| Concrete evidence exists | Create a finding with file, lines, symbol, benefit, validation, and rollback. |
| Evidence is incomplete | Mark as hypothesis and lower confidence. |
| Recommendation is cosmetic or speculative | Omit it unless maintainability benefit is clear. |