clone detection skills

7 tagged clone detection, measured the same way as everything else here.

Browse within: static-analysis 5

architecture-review

01

ludo-technologies/pyscn

Skill Claude CodeCodex

Analyze Python module architecture using pyscn - class coupling (CBO), cohesion (LCOM), dependency cycles, and module communities. Use when user asks about architecture, module structure, coupling, circular dependencies, or which files to review or change together.

1.0k 3d ago A 53 tokens original MIT

cli-analysis

02

ludo-technologies/pyscn

Skill Claude CodeCodex

Run the pyscn command-line tool for Python code quality analysis - CI/CD quality gates, HTML/JSON/CSV reports, full analysis runs, and project configuration. Use when user wants a CI check, a shareable report file, or to configure pyscn for a project.

1.0k 3d ago A 59 tokens original MIT

health-check

03

ludo-technologies/pyscn

Skill Claude CodeCodex

Get an overall Python code quality health score using pyscn. Use when user asks how healthy or good the code is, wants a quality overview, a grade, a summary of technical debt, or a before/after quality comparison.

1.0k 3d ago A 49 tokens original MIT

erase

04

skymanbp/CodeEraser

Skill Claude CodeCodex

Guided cleanup of CodeEraser findings — read the reports, verify every candidate against the actual code, delete safely, and prove convergence with ce check. Invoke when the user asks to clean up duplication, dead code, or act on CodeEraser findings.

20 yesterday A 56 tokens original Apache-2.0

weavatrix

05

Weavatrix/weavatrix

Skill Claude CodeCodex

Use the Weavatrix MCP when a repository task benefits from indexed evidence: codebase orientation, symbol/source search, dependency or call graphs, change impact, API/event tracing, architecture checks, Git/coverage evidence, duplicates, dead-code review, or semantic context. Skip it for trivial single-file edits or…

4 yesterday A 78 tokens original MIT

weavatrix

06

Weavatrix/weavatrix

Skill Claude CodeCodex

Use the Weavatrix MCP when a repository task benefits from indexed evidence: codebase orientation, symbol/source search, dependency or call graphs, change impact, API/event tracing, architecture checks, Git/coverage evidence, duplicates, dead-code review, or semantic context. Skip it for trivial single-file edits or…

4 yesterday A 78 tokens copy · 100% MIT