Review dry
Review codebase for DRY (duplication) issuesFrom its SKILL.md
npx -y skills add yida29/archrip --skill review-dryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, as published. Nobody here has run it
DRY review — duplication, single source of truth
Review the target codebase with a DRY lens and report actionable duplication.
Scope
Use $ARGUMENTS to decide scope:
- If it mentions
git diff/ PR / commit: focus on changed areas first. - If it mentions a path: review that subtree.
- If empty: scan the repository for high-impact duplication.
What to look for (examples)
- Duplicated types/interfaces across packages
- Duplicated constants (paths, magic strings, category metadata, colors)
- Duplicated validation rules / parsing logic
- Repeated error messages and CLI usage guidance
- Copy-pasted command steps (install/build/serve)
Output format
Produce:
- Top duplications (priority order)
- Evidence: file paths + short excerpt references
- Why it hurts (change amplification / inconsistency risk)
- Smallest refactor that removes duplication (shared module, helper, constant)
- Quick wins (low effort, high payoff)
- Risks of over-abstraction (what NOT to DRY)
$ARGUMENTS