verify-quality

Analyze codebases for complexity, duplication, naming, and length issues.

5|1|Updated Apr 8, 2026

Search Tags:#refactoring #complexity #code-quality #static-analysis #lint #ci

Ready to run

npx skills add https://github.com/Catsofsuffering/CCGS --skill verify-quality-catsofsuffering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-quality
Source: https://github.com/Catsofsuffering/CCGS/tree/main/templates/skills/tools/verify-quality
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill verify-quality-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects and quantifies code quality issues such as high complexity, duplicated code, naming violations, excessive function or file length, and large parameter lists to reduce technical debt and prevent bug-prone code from being merged.

Core Features & Use Cases

Automated scanning of repositories to compute complexity metrics, function/file length, comment density, and simple duplication signals.
Language coverage for Python and common compiled/script languages with special parsing for Python functions and classes.
Outputs human-readable reports and optional machine-readable JSON for CI integration.
Use cases: run during PR review, before commits, after large refactors, or as part of CI to enforce quality gates and provide refactoring guidance.

Quick Start

Run the verify-quality skill to scan a project path and generate a JSON quality report highlighting complexity, naming, and duplication issues.

Frequently Asked Questions about verify-quality

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

FAQPage Schema

How do I automate code quality checks and refactoring verification in a CI pipeline?▼

Automate code quality checks by scanning repositories to compute complexity metrics, function length, and duplication signals, generating human-readable reports or optional JSON output for CI integration. You can run this during PR review, before commits, or after large refactors to enforce quality gates.

What code quality metrics should I enforce to reduce technical debt?▼

To reduce technical debt, enforce thresholds for cyclomatic complexity, function and file length, parameter counts, and naming conventions. Tracking these metrics detects duplicated code and prevents bug-prone code from being merged.

Does static analysis for code complexity support multi-language projects including Python and Go?▼

Static analysis for code complexity supports multi-language projects including Python, JavaScript, TypeScript, Go, Java, Rust, C, and C++. It includes special parsing for Python functions and classes.

Can I generate a JSON quality report for cyclomatic complexity and naming violations?▼

You can generate an optional machine-readable JSON quality report alongside human-readable reports. This JSON output highlights cyclomatic complexity, naming violations, duplication signals, and comment density for CI integration.

What is the best way to detect duplicated code and naming conventions before a commit?▼

Detect duplicated code and naming convention violations by running automated repository scans as a pre-commit check. These scans compute simple duplication signals and enforce naming thresholds to provide refactoring guidance.

When do I need to run a lint and complexity scan after a refactor?▼

Run a lint and complexity scan after large refactors to verify that changes have not introduced high complexity, excessive file length, or large parameter lists, ensuring the refactor successfully reduced technical debt.