refactor-analysis

스타85

포크3

업데이트2026년 4월 4일 05:13

Run cargo-coupling and similarity-rs to identify refactoring targets, then create a prioritized plan.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

nwiizo

nwiizo/claudelytics

다운로드

Refactor Analysis

Analyze code coupling and duplication, then create a prioritized refactoring plan.

Coupling analysis:
```
cargo coupling --exclude-tests --ai --hotspots=10
```
Focus on: High Afferent (too many dependents), God Modules, circular deps.
Similarity scan:
```
similarity-rs ./src --min-tokens 50
```
Focus on: 95%+ similarity pairs, extract shared functions.
Combine findings into a prioritized plan:
- High: modules with >20 dependents, circular deps
- Medium: God modules (>30 functions or >500 lines), 100% duplicates
- Low: 90%+ similarity, primitive obsession
Create GitHub issues for each refactoring target with refactoring label.
Execute high-priority items if requested, verifying with cargo test after each change.

이 저장소의 다른 Skills

같은 저장소

Run full quality gate before release — fmt, clippy, test, mutants, similarity, coupling.

Systematic bug investigation and fix workflow. Use when fixing bugs, investigating issues, or debugging test failures.

Pre-release verification workflow - version, security audit, performance, cross-platform builds, documentation.

Development environment setup - Rust toolchain, cross-compilation targets, dependencies, git hooks, IDE config.

Split complex tasks into sequential steps with parallel subtasks. Use for multi-step workflows needing dependency ordering and adaptive planning.

Comprehensive quality assurance - tests, linting, formatting, code analysis, and release build verification.

name	refactor-analysis
description	Run cargo-coupling and similarity-rs to identify refactoring targets, then create a prioritized plan.

Analyze code coupling and duplication, then create a prioritized refactoring plan.

Coupling analysis:
```
cargo coupling --exclude-tests --ai --hotspots=10
```
Focus on: High Afferent (too many dependents), God Modules, circular deps.
Similarity scan:
```
similarity-rs ./src --min-tokens 50
```
Focus on: 95%+ similarity pairs, extract shared functions.
Combine findings into a prioritized plan:
- High: modules with >20 dependents, circular deps
- Medium: God modules (>30 functions or >500 lines), 100% duplicates
- Low: 90%+ similarity, primitive obsession
Create GitHub issues for each refactoring target with refactoring label.
Execute high-priority items if requested, verifying with cargo test after each change.