code-quality

Name: code-quality
Availability: InStock
Author: dhamija

Apply a structured checklist to review code for correctness, readability, security, performance, and maintainability.

Updated Jan 25, 2026

Search Tags:#security #maintainability #code-quality #static-analysis #code-review #pull-request

Ready to run

npx skills add https://github.com/dhamija/claude-workflow-agents --skill code-quality-dhamija

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/dhamija/claude-workflow-agents/tree/main/templates/skills/code-quality
Command: npx skills add https://github.com/dhamija/claude-workflow-agents --skill code-quality-dhamija

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework for evaluating code quality during reviews and gate-keeping in CI, ensuring consistency across projects.

Core Features & Use Cases

Code correctness assessment: verify logic, edge cases, and tests.
Readability and maintainability: emphasis on naming, comments, formatting, and modular design.
Use Case: A team wants a repeatable checklist to review pull requests before merging.

Quick Start

Use the code-quality skill to perform a structured review of a PR or code snippet, applying the criteria for correctness, readability, security, performance, and maintainability.

Frequently Asked Questions about code-quality

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

FAQPage Schema

How do I enforce code quality standards during pull request reviews?▼

Code quality enforcement during pull requests uses a structured checklist to assess correctness, readability, security, performance, and maintainability consistently. This standardized approach ensures all reviews apply the same criteria before code merges, reducing inconsistencies across your team.

What should I check for in a code review to ensure maintainability?▼

Code review for maintainability focuses on naming conventions, code comments, formatting consistency, and modular design. These elements make code easier to understand and modify later, reducing technical debt and onboarding friction for new team members.

Can I use a code quality checklist for both pull requests and code snippets?▼

Yes, code quality review applies to both pull requests and isolated code snippets across software engineering projects. The same structured evaluation framework covers correctness, readability, security, performance, and maintainability regardless of context or scope.

How does static analysis fit into code quality reviews?▼

Static analysis complements manual code review by automatically detecting potential issues without executing code. Combined with a structured review checklist, it catches security vulnerabilities, correctness problems, and style violations, strengthening overall code quality gates.

What's the difference between a code quality review and security review?▼

Code quality review evaluates correctness, readability, performance, and maintainability holistically, while security review focuses specifically on vulnerabilities and access control risks. A comprehensive checklist incorporates security assessment as one dimension of broader quality evaluation.

Do I need team alignment before implementing a code quality checklist?▼

Yes, a standardized code quality checklist requires team agreement on evaluation criteria and remediation expectations. Explicit documentation of issues and consistent application across pull requests ensures the checklist functions as an effective gate-keeping mechanism.