skills.rest
acardozzo
acardozzoCOMMUNITY
Explore all skills by this author →
GitHub

code-rx

Evaluate code quality against ISO 25010, SQALE, and SonarQube standards.

Updated Mar 15, 2026
Search Tags:#code quality#architecture#code review#refactoring#metrics#technical debt
One-click install
npx skills add https://github.com/acardozzo/rx-suite --skill code-rx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-rx
Source: https://github.com/acardozzo/rx-suite/tree/main/skills/code-rx
Command: npx skills add https://github.com/acardozzo/rx-suite --skill code-rx

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a metric-driven, objective, and repeatable evaluation of code quality, helping to identify technical debt and areas for improvement.

Core Features & Use Cases

  • Objective Scoring: Evaluates code against 8 dimensions and 29 sub-metrics with precise thresholds.
  • Prioritized Recommendations: Generates scorecards, opportunity maps, and per-dimension improvement plans.
  • Use Case: When you need to understand the quality of a specific module, compare codebases before and after refactoring, or validate progress towards technical goals.

Quick Start

Use the code-rx skill to evaluate the quality of the src/core directory.

Frequently Asked Questions about code-rx

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

FAQPage Schema
How do I objectively measure code quality and technical debt?▼

Code quality is measured objectively using a metric-driven framework based on ISO 25010, SQALE, and SonarQube standards. This evaluates modularity, dependency health, complexity, and duplication to generate detailed scorecards and identify technical debt.

What metrics are used to evaluate code architecture and modularity?▼

Code architecture is evaluated using 29 sub-metrics across 8 dimensions, focusing on modularity, abstraction levels, dependency health, test quality, complexity, and type safety. These metrics identify structural weaknesses and prioritize refactoring opportunities.

Can I score a specific source code directory instead of the entire codebase?▼

Yes, you can evaluate code quality across specified code layers or the entire codebase. Targeting a specific source directory like src/core produces a focused scorecard and improvement plan for that module.

How do I validate progress after a code refactoring?▼

Validating refactoring progress involves comparing metric-driven scorecards before and after the changes. The evaluation generates an opportunity map and per-dimension improvement plans to verify if technical debt decreased.

What is the best way to identify security and type safety issues in my code?▼

The best way to identify security and type safety issues is through an automated evaluation against SQALE and SonarQube standards. This analysis highlights top issues across specified code layers and generates actionable improvement plans.

Related Skills

Explore More Software Engineering Skills→
JaiminVadadoriyaJaiminVadadoriya
1

analyzing-dotnet-performance

Detect and classify performance anti-patterns in .NET source code.

Community
Advanced
aquariuscookaquariuscook

refactoring-patterns

Apply behavior-preserving refactoring patterns to address code smells.

Community
Advanced
vuralserhat86vuralserhat86
43

quality_validator

Validate deliverables against quality standards and compliance requirements before shipping.

Community
Advanced
Purushot14Purushot14
7

review

Review Python working changes with linters and generate a findings report.

Community
Intermediate