code-quality-analyst

Identify code smells with severity scoring and generate a prioritized refactoring roadmap.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill code-quality-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-analyst
Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/code-quality-analyst
Command: npx skills add https://github.com/jikig-ai/soleur --skill code-quality-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases often accumulate undetected smells that degrade maintainability and reliability. This Skill formalizes detection and provides severity-scored findings plus a prioritized refactoring roadmap.

Core Features & Use Cases

  • Formal smell detection following Fowler's methodology with severity scoring.
  • Smell-to-refactoring mappings and a prioritized roadmap.
  • End-to-end code review support for planning and execution phases.

Quick Start

Provide a codebase path to analyze and I will generate a formal report with a prioritized refactor plan.

Frequently Asked Questions about code-quality-analyst

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

FAQPage Schema
How do I detect code smells and generate a refactoring roadmap?

Code smell detection applies Fowler's methodology to identify maintainability issues in your codebase, producing a formal report with severity scoring and a prioritized refactoring roadmap.

What is the best way to prioritize refactoring tasks across a large codebase?

Refactoring prioritization uses severity scoring to rank identified code smells, mapping each smell to specific refactoring actions and generating a structured roadmap with risk assessments.

Can I perform code review and smell detection across different programming languages?

Smell detection applies to libraries, services, and modules across languages, analyzing the target codebase path to deliver structured code quality reports with traceable refactor guidance.

How does severity scoring work for code smell analysis?

Severity scoring evaluates detected code smells using Fowler's methodology, assigning severity levels to each finding to formalize reporting and enable traceable mappings from smells to refactorings.

What do I need to provide to start a code quality analysis?

Code quality analysis requires a codebase path to analyze, which triggers formal smell detection and generates a prioritized refactor plan with clear dependencies and risk assessments.

When do I need formal code quality reporting instead of a basic code review?

Formal code quality reporting is needed when you require traceable mappings from detected smells to specific refactorings, severity scoring, and clear risk assessments for planning and execution phases.