skills.rest
selcukyucel
selcukyucelCOMMUNITY
Explore all skills by this author →
GitHub

refactoring-analyzer

Identify refactoring opportunities, code smells, and architectural violations in code modules and files.

7|2|Updated Feb 7, 2026
Search Tags:#architecture#refactoring#quality#static-analysis#analyze#software-engineering#code-smells
One-click install
npx skills add https://github.com/selcukyucel/north-starr --skill refactoring-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactoring-analyzer
Source: https://github.com/selcukyucel/north-starr/tree/main/skills/refactoring-analyzer
Command: npx skills add https://github.com/selcukyucel/north-starr --skill refactoring-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically surface refactoring opportunities by analyzing modules and files for code smells, architectural violations, and maintainability risks across languages and frameworks.

Core Features & Use Cases

  • Detect common code smells, anti-patterns, and architectural violations
  • Propose targeted refactoring steps, design fixes, and architecture improvements
  • Provide scope-limited analysis at module or file level to aid focused reviews

Quick Start

Analyze a target module or file path to obtain a structured refactoring assessment and remediation plan.

Frequently Asked Questions about refactoring-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify code smells and refactoring opportunities in my software architecture?▼

To identify code smells, you analyze modules and files for anti-patterns and architectural violations. This process detects maintainability risks and reports targeted refactoring steps to improve overall software quality across any language or framework.

What is the best way to perform a static analysis for code smells on a specific module?▼

The best way to perform static analysis on a specific module is applying a scope-limited review. This detects architectural violations and code smells at the file or module level, providing an actionable remediation plan without analyzing the entire codebase.

Can I use static analysis to find architectural violations across different programming languages?▼

Yes, you can find architectural violations across different programming languages. The analysis detects code smells and applies a refactoring checklist regardless of the framework, identifying structural issues in any software module.

How do I get actionable remediation steps after detecting anti-patterns in my code?▼

To get actionable remediation steps after detecting anti-patterns, you run a structured workflow that includes scoping, language detection, and impact analysis. This yields targeted design fixes and architecture improvements for the identified code smells.

Does code smell detection work for both module-level and file-level scopes?▼

Code smell detection works for both module-level and file-level scopes. This targeted analysis approach helps developers focus on specific sections of a project, identifying refactoring opportunities and maintainability risks without evaluating unrelated code.

Related Skills

Explore More Software Engineering Skills→
AirMileAirMile

core-setup

Automate end-to-end project setup within Claude Code.

Community
Advanced
djpTester44djpTester44

refactor-guru

Refactor code to enforce SOLID, DRY, and readability principles.

Community
Intermediate
InverterNetworkInverterNetwork

requesting-code-review

Automates pre-commit code verification through static security analysis, linting, and independent review.

Official
Advanced
notquenotque
415

universal-quality-gate

Detect project languages via marker files and run configured linters and analyzers.

Community
Advanced