refactor-structural-duplication

Identify structurally duplicate logic (pipeline-spine duplication) across semantically distinct modules. Use when multiple implementations share the same orchestration skeleton (e.g., bounds→shape→chunking→reduction→wrap), and unification may require subtle abstraction. Produces a duplication map and a safe extraction/refactor plan.

⭐5stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026

When & Why to Use This Skill

This Claude skill specializes in identifying structural duplication—known as pipeline-spine duplication—across semantically distinct modules. It goes beyond simple copy-paste detection by analyzing shared orchestration skeletons (such as data processing sequences) to prevent code drift. The skill provides developers with a detailed duplication map and a staged, safe refactoring plan to unify logic through sophisticated architectural abstraction.

Use Cases

  • Case 1: Identifying parallel data processing pipelines (e.g., bounds → shape → chunking) across different domain modules to ensure architectural consistency and reduce technical debt.
  • Case 2: Generating a safe extraction and refactor plan when a developer is about to re-implement existing infrastructure logic for a new product or feature.
  • Case 3: Auditing complex codebases for 'hidden' structural similarities where domain concepts differ but the underlying execution flow is identical, facilitating cleaner system design.
namerefactor-structural-duplication
licenseMIT
description>
authorJordan Godau

Instructions

Read all references in references/ before starting.

Goal

Detect and report structural duplication across modules (not copy/paste), especially where:

  • different domain concepts remain correctly separate, but
  • the underlying processing pipeline is parallel/duplicated, risking drift.

When unification likely requires subtle abstraction, produce a staged plan that can be executed safely.

Scope

  • This skill does not enforce “thin public facades” or restructure public APIs.
  • This skill does identify shared pipeline spines and propose extraction targets and abstraction seams.

Signals

Activate when any of the following are true:

  • Multiple modules implement similar orchestration stages (even with different operators).
  • There are parallel implementations of structurally similar functionality in the codebase.
  • The agent (or a developer) is about to re-implement “the same infrastructure again” for a new product.

Procedure

Follow references/03_PROCEDURE.md.

Output

Produce a single Markdown report using references/05_OUTPUT_TEMPLATE.md. If abstraction is needed, include a staged plan using references/04_REFACTOR_PLAN_TEMPLATE.md.