verify-quality

Analyze code quality metrics for complexity, naming, and duplication across repositories.

238|30|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/telagod/code-abyss --skill verify-quality-telagod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-quality
Source: https://github.com/telagod/code-abyss/tree/main/skills/tools/verify-quality
Command: npx skills add https://github.com/telagod/code-abyss --skill verify-quality-telagod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates detection and reporting of code quality issues across a codebase, helping teams reduce technical debt and improve maintainability.

Core Features & Use Cases

  • Multi-language code quality scanning including complexity, naming, and duplication metrics.
  • Generates actionable guidance for developers and reviewers, suitable for CI checks and pre-merge quality gates.
  • Use Case: Run nightly scans on a repository to surface hotspots, then apply recommended refactors before release.

Quick Start

Run node skills/tools/verify-quality/scripts/quality_checker.js <path> to scan your repository and generate a quality report.

Frequently Asked Questions about verify-quality

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

FAQPage Schema
How do I automate static analysis for code quality in a multi-language repository?

To automate static analysis for code quality, run the quality checker script against your repository path to compute complexity, naming, and duplication metrics, generating a detailed report to reduce technical debt.

What code quality metrics are most useful for identifying refactoring hotspots?

Useful code quality metrics for refactoring include complexity, naming conventions, and code duplication, which surface maintainability hotspots and provide actionable recommendations for developers.

Can I integrate code quality scanning into CI workflows as a pre-merge quality gate?

Yes, you can integrate code quality scanning into CI workflows as a pre-merge quality gate by optionally emitting machine-readable JSON output, enabling automated checks before release.

Do I need to install external dependencies to run the code complexity analysis?

No, you do not need external dependencies to run code complexity analysis, as the standalone Node.js script parses common source files and computes quality metrics directly without additional setup.

What is the best way to surface code duplication and technical debt across a codebase?

The best way to surface code duplication and technical debt is running a nightly scan across your codebase to identify hotspots, then applying the recommended refactors before release.