skills.rest
gotekna
goteknaCOMMUNITY
Explore all skills by this author →
GitHub

duplicate-detector

Detect duplicated implementations and SSoT violations across Rails codebases during reviews and refactoring.

Updated Nov 10, 2025
Search Tags:#code-quality#consolidation#code-review#ssot#duplicate#regression-prevention
One-click install
npx skills add https://github.com/gotekna/Teeem --skill duplicate-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: duplicate-detector
Source: https://github.com/gotekna/Teeem/tree/main/.claude/skills/duplicate-detector
Command: npx skills add https://github.com/gotekna/Teeem --skill duplicate-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects duplicated code patterns and SSoT violations to keep a DRY, maintainable codebase.

Core Features & Use Cases

  • Detects duplicate implementations across backend and frontend
  • Identifies SSoT violations and guides consolidation
  • Provides workflow guidance to review before adding new logic, constants, or configs
  • Supports design reviews and refactoring to reduce regressions
  • Recommends registration or referencing existing implementations

Quick Start

Ask Claude to scan your codebase for duplicates and SSoT violations before making any changes.

Frequently Asked Questions about duplicate-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect duplicate code patterns across frontend and backend?▼

Identifying duplicate code patterns involves scanning your codebase during design reviews to catch overlapping backend and frontend implementations, guiding consolidation and safe reuse before introducing new logic.

What is an SSoT violation and how do I prevent it in a Rails codebase?▼

An SSoT violation happens when logic, constants, or configs are duplicated rather than referencing a single source of truth. Prevent it by reviewing existing implementations and registering or referencing them before adding new logic.

When do I need to check for code duplication before refactoring?▼

Check for code duplication before refactoring when modifying existing logic, consolidating overlapping implementations first to reduce regressions and maintain a DRY, maintainable codebase.

Can I use this duplicate detection approach for general software projects or only Rails?▼

This duplicate detection approach applies to both Rails and general software projects during design reviews, code changes, and refactoring to ensure consistency and detect duplicates across the stack.

What's the best way to consolidate duplicated implementations and maintain a DRY codebase?▼

To consolidate duplicated implementations, scan for overlapping patterns, identify SSoT violations, and recommend referencing or registering existing logic before introducing new code to maintain a DRY codebase.

Why does duplicated logic cause regression prevention issues during code changes?▼

Duplicated logic causes regression issues because updating one implementation without finding all duplicates leads to inconsistent behavior and broken functionality during code changes.

Related Skills

Explore More Software Engineering Skills→
bs-koobs-koo

reverse-scan-source

Scan source code projects to reverse-engineer DE-05 program definitions.

Community
Advanced
kirtikirti
1

duplicate-code-detection

Detect duplicate JavaScript/TypeScript code blocks across files and modules.

Community
Advanced
oogDZoogDZ

principles-validate

Validate Python code compliance with SSOT, DRY, naming and structure principles.

Community
Intermediate
santosomarsantosomar
1

code-pattern-extractor

Detect idioms, clones, and anti-patterns in codebases via AST analysis.

Community
Intermediate