Generate concrete refactoring proposals with Before/After code based on coupling analysis results.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add nwiizo/cargo-coupling --skill refactor --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Refactor?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nwiizo-refactor)More formats (shields.io, HTML) on the badges page.
---
name: refactor
description: Generate concrete refactoring proposals with Before/After code based on coupling analysis results.
argument-hint: [path] [issue-type: global-complexity|cascading-change|inappropriate-intimacy|high-efferent|high-afferent|all]
---
# Refactor - Refactoring Proposals
## Execution Steps
1. Run `cargo run -- coupling $ARGUMENTS` to analyze
2. Identify specified issue type (default: all)
3. Propose refactoring steps with Before/After code examples
4. Present priority table and phased migration plan
## Issue Types
| Type | Description |
|------|-------------|
| `global-complexity` | Strong coupling to distant modules |
| `cascading-change` | Coupling to volatile modules |
| `inappropriate-intimacy` | Internal access across boundaries |
| `high-efferent` | Too many outgoing dependencies |
| `high-afferent` | Too many incoming dependencies |
| `all` | All issue types (default) |
## Verification
```bash
# Before refactoring
cargo run -- coupling --summary ./src > before.txt
# After refactoring
cargo run -- coupling --summary ./src > after.txt
# Compare
diff before.txt after.txt
```
## Guidelines
- Split large changes into small commits
- Verify tests pass at each step
- Document change intent for reviewers
Code pattern examples: [patterns.md](patterns.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
一个全面的 Claude Code 会话验证系统。
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.