quality-analyst

Assess code quality and quantify technical debt across a codebase.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ImaginerLabs/skill-manager --skill quality-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-analyst
Source: https://github.com/ImaginerLabs/skill-manager/tree/main/skills/agent/quality-analyst
Command: npx skills add https://github.com/ImaginerLabs/skill-manager --skill quality-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many engineering teams lack a consistent, data-driven way to quantify code quality and prioritize technical debt, which leads to hidden maintenance costs and unpredictable refactors. This Skill provides objective measurements and actionable guidance so teams can make informed decisions about testing, refactoring, and sprint planning.

Core Features & Use Cases

  • Quality assessment: Generate an overall quality score and per-dimension breakdown (maintainability, complexity, coverage, duplication, documentation).
  • Technical debt tracking: Identify, classify, and prioritize technical debt items with estimated remediation effort and suggested owners.
  • Test coverage & complexity analysis: Highlight uncovered critical paths, low-coverage modules, and complexity hotspots for targeted testing and refactoring.
  • Use cases: Weekly quality reports for engineering leadership, pre-release risk assessments, and sprint planning inputs for debt repayment.

Quick Start

Ask Metric to evaluate the codebase at ./ and generate a comprehensive quality report with prioritized technical debt and actionable refactor suggestions.

Frequently Asked Questions about quality-analyst

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

FAQPage Schema
How do I quantify technical debt across my codebase for sprint planning?

To quantify technical debt, you can analyze your software repository to identify, classify, and prioritize debt items with estimated remediation effort and suggested owners for sprint planning.

How do I generate a code quality report with maintainability and complexity scores?

Generate a code quality report by assessing the repository to produce an overall quality score and per-dimension breakdowns for maintainability, complexity, test coverage, duplication, and documentation.

What is the best way to identify complexity hotspots and uncovered critical paths?

Identify complexity hotspots and uncovered critical paths by running test coverage and complexity analysis on your codebase to highlight low-coverage modules for targeted testing and refactoring.

Can I use this for pre-release risk assessments and weekly engineering leadership reports?

Yes, you can use the structured quality reports highlighting maintainability scores and debt prioritization for weekly engineering leadership updates and pre-release risk assessments.

Does the code analysis provide actionable refactor suggestions for engineering uptake?

Yes, the code analysis produces structured reports with suggested remediation steps and actionable refactor suggestions suitable for direct engineering uptake and implementation.