refactoring-analyzer

Name: refactoring-analyzer
Availability: InStock
Author: foo-x

Analyze project code for refactoring needs and generate a Markdown report.

2|1|Updated Feb 2, 2019

Search Tags:#code quality #code review #code analysis #refactoring #software design #technical debt

Ready to run

npx skills add https://github.com/Foo-x/dotfiles --skill refactoring-analyzer-foo-x

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactoring-analyzer
Source: https://github.com/Foo-x/dotfiles/tree/main/claude/skills/refactoring-analyzer
Command: npx skills add https://github.com/Foo-x/dotfiles --skill refactoring-analyzer-foo-x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies areas in your codebase that require refactoring, helping you improve code quality, reduce technical debt, and enhance maintainability.

Core Features & Use Cases

Codebase Analysis: Analyzes code for programming principle violations, code smells, quality metrics, and test code quality.
Refactoring Suggestions: Provides concrete suggestions and improved code examples for identified issues.
Use Case: Before a major feature release, use this Skill to perform a comprehensive code review, identify potential issues, and prioritize refactoring efforts to ensure a cleaner, more robust codebase.

Quick Start

Analyze the current project for refactoring opportunities.

Frequently Asked Questions about refactoring-analyzer

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

FAQPage Schema

How do I analyze my codebase for refactoring needs and technical debt?▼

To analyze code for refactoring needs, this Skill systematically explores your project to identify principle violations, code smells, quality metrics, and test quality issues, integrating the findings into a comprehensive Markdown report.

What is the best way to visualize technical debt before a major feature release?▼

The best way to visualize technical debt is by running a comprehensive code review that assesses code quality metrics and identifies code smells, resulting in a detailed Markdown report that highlights areas requiring immediate refactoring.

How does code analysis identify violations of software design principles?▼

Code analysis identifies software design principle violations by deploying sub-agents to perform multi-faceted checks across your codebase, evaluating the source code against established programming principles and generating concrete improvement suggestions.

Can I get concrete refactoring suggestions and improved code examples for code smells?▼

Yes, you can get concrete refactoring suggestions and improved code examples. The analysis identifies specific code smells and provides actionable recommendations to enhance maintainability and reduce technical debt.

Does the code review process evaluate test code quality as well as source code?▼

Yes, the code review process evaluates test code quality. It uses specialized sub-agents to assess your tests alongside source code metrics, ensuring a comprehensive assessment of overall project health and refactoring needs.

When should I perform a code quality analysis to assess refactoring needs?▼

You should perform code quality analysis before major feature releases or when addressing accumulated technical debt, using the generated Markdown report to prioritize refactoring efforts and ensure a robust, maintainable codebase.