code-quality

Automate code quality reviews with a 25-point checklist for structure, errors, security, performance, and testing.

2|1|Updated Nov 17, 2025

Search Tags:#testing #security #review #code-quality #lint

Ready to run

npx skills add https://github.com/xbklairith/kisune --skill code-quality-xbklairith

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/xbklairith/kisune/tree/main/dev-workflow/skills/code-quality
Command: npx skills add https://github.com/xbklairith/kisune --skill code-quality-xbklairith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A thorough pre-commit code quality review that catches issues and suggests refactors.

Core Features & Use Cases

SRP, DRY, Naming: Code quality checks
Error Handling & Security: Validation, SQL injection protection
Testing Guidance: Ensuring tests exist and cover edge cases

Quick Start

Run the code-quality review before committing or during PRs.

Frequently Asked Questions about code-quality

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

FAQPage Schema

How do I automate code quality checks before committing?▼

Automate code quality checks by running pre-commit reviews that scan for structural issues, errors, security vulnerabilities, and testing gaps using a 25-point checklist. This catches problems early in development, reducing refactoring overhead and ensuring maintainability before code reaches version control.

What does a code quality review checklist typically cover?▼

A comprehensive code quality review covers five dimensions: structure (SRP, DRY, naming conventions), error handling, security (SQL injection, validation), performance, and testing adequacy. This structured approach ensures consistent standards across pre-commit checks, feature branches, refactoring sessions, and post-merge validation.

Can code quality reviews suggest specific refactorings with examples?▼

Yes, code quality reviews can identify refactoring opportunities and provide concrete examples to improve code maintainability. Suggestions target naming clarity, DRY violations, SRP breaches, and testing coverage, helping developers understand not just what to fix but how to fix it effectively.

When should I run code quality reviews in my development workflow?▼

Run code quality reviews at multiple stages: before committing locally, during feature development, throughout refactoring sessions, and after merging to main. Early detection at pre-commit stage prevents bad practices from entering the codebase; post-merge validation ensures standards compliance across all branches.

How do code quality reviews enforce security best practices?▼

Security enforcement checks for validation gaps, SQL injection vulnerabilities, and improper error handling that could expose sensitive data. By catching these issues during review rather than production, code quality checks reduce attack surface and compliance risk.

Do I need existing tests to run a code quality review?▼

No, but code quality reviews specifically assess whether tests exist and adequately cover edge cases. If tests are missing or incomplete, the review identifies gaps and guides you to add appropriate test coverage alongside your feature code.