Run any Skill in Manus with one click

refactor-structural-duplication

Stars6

Forks1

UpdatedJanuary 9, 2026 at 17:48

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

JordanGunn

JordanGunn/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

6 files

SKILL.md

readonly

name	refactor-structural-duplication
license	MIT
description	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.
metadata	{"author":"Jordan Godau","references":["01_INTENT.md","02_DEFINTIONS.md","03_PROCEDURE.md","04_REFACTOR_PLAN_TEMPLATE.md","05_OUTPUT_TEMPLATE.md"],"keywords":["duplication","structural","pipeline","spine","extraction","abstraction","unification","drift"]}

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.

More from this repository

same repository

prompt

JordanGunn/skills

Orchestrator skill for the `prompt` skillset. Dispatches to member skills in a safe, predictable order. Separates intent formation from execution to protect humans from premature or misaligned execution.

2026-01-106

doctor-exam

JordanGunn/skills

Conduct a focused, evidence-driven examination of ONE triaged suspect area. This is a test, not a verdict. Evidence may falsify the leading hypothesis.

2026-01-096

doctor-intake

JordanGunn/skills

Convert the user's raw description into a clinically precise intake note suitable for handoff to another agent or human. Captures symptoms, normalizes terminology, and separates observation from belief.

2026-01-096

doctor

JordanGunn/skills

Orchestrator skill for the `doctor` skillset. A diagnostic protocol that models software failures as medical cases — preventing premature action, wrong-layer fixation, and false certainty in complex codebases.

2026-01-096

doctor-treatment

JordanGunn/skills

Produce a treatment note that combines diagnosis, confidence, supporting evidence, alternative explanations, and proposed treatment options. Creates an artifact, not execution.

2026-01-096

doctor-triage

JordanGunn/skills

Perform breadth-first hypothesis surfacing and prioritization across all ownership zones, without commitment. This is not diagnosis and not investigation.

2026-01-096

name	refactor-structural-duplication
license	MIT
description	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.
metadata	{"author":"Jordan Godau","references":["01_INTENT.md","02_DEFINTIONS.md","03_PROCEDURE.md","04_REFACTOR_PLAN_TEMPLATE.md","05_OUTPUT_TEMPLATE.md"],"keywords":["duplication","structural","pipeline","spine","extraction","abstraction","unification","drift"]}

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.