code-quality-lens

Evaluate code quality and maintainability across codebases without executing code.

30|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/atomicinnovation/accelerator --skill code-quality-lens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-lens
Source: https://github.com/atomicinnovation/accelerator/tree/main/skills/review/lenses/code-quality-lens
Command: npx skills add https://github.com/atomicinnovation/accelerator --skill code-quality-lens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers and review orchestrators identify maintainability barriers in code by assessing readability, complexity, error handling, and testability so future maintainers can work with confidence.

Core Features & Use Cases

  • Complexity & Readability Assessment: Flags high cyclomatic/cognitive complexity, deep nesting, long methods, unclear naming, and opportunities for guard clauses or refactoring.
  • Design Principle Evaluation: Checks for SOLID, SRP, DRY, KISS, YAGNI adherence and whether abstractions and composition are appropriate.
  • Error Handling & Observability Review: Identifies swallowed exceptions, poor error categorization, missing context in logs, and gaps in observability.
  • Testability Focus: Evaluates whether components support isolated testing (dependency injection, interfaces) and highlights coupling that impedes tests.
  • Usage: Intended for integration into review orchestrators and automated review pipelines; not invoked directly by end users.

Quick Start

Ask the review orchestrator to run the code-quality-lens against the target files or repository path to produce a maintainability-focused report with confidence-rated findings.

Frequently Asked Questions about code-quality-lens

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

FAQPage Schema
How do I check code readability and maintainability during a code review?

To check code readability and maintainability, inspect source files to identify code smells, high cyclomatic complexity, deep nesting, and unclear naming. This process flags design principle violations and error handling deficiencies, providing concise, confidence-rated refactoring recommendations.

What is the best way to evaluate testability and coupling in my codebase?

Evaluating testability requires inspecting components for dependency injection and interface usage to ensure isolated testing. This analysis highlights excessive coupling that impedes tests and provides confidence-rated recommendations to improve component design.

How do I identify swallowed exceptions and poor error handling in source files?

Identify swallowed exceptions and poor error handling by inspecting source files for missing log contexts and poor error categorization. This review exposes observability gaps and provides targeted recommendations to improve error handling robustness.

Can I use an automated review pipeline to find SOLID, DRY, and KISS design violations?

Yes, you can use automated review pipelines to find SOLID, DRY, and KISS violations. The evaluation checks whether abstractions and composition are appropriate, flagging design principle violations and generating a maintainability-focused report with confidence-rated findings.

Does a code quality assessment require executing the codebase?

No, a code quality assessment does not require executing the codebase. The evaluation strictly relies on inspecting source files to assess complexity, readability, and testability, delivering concise refactoring recommendations without running the code.