Verified:GitHub

code-quality

Enforce code-quality guidelines for naming, function size, and error handling.

Updated Jan 24, 2026

Search Tags:#refactoring #maintainability #code-quality #code-review #software-engineering #clean-code #solid-principles

Ready to run

npx skills add https://github.com/jaeyeonling/opencode-kit --skill code-quality-jaeyeonling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/jaeyeonling/opencode-kit/tree/main/.opencode/skills/code-quality
Command: npx skills add https://github.com/jaeyeonling/opencode-kit --skill code-quality-jaeyeonling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality issues slow development due to unclear naming, bloated functions, noisy or misleading comments, fragile error handling, and inconsistent refactoring. This skill provides a structured approach to enforce clean code practices across a codebase and align teams on a shared standard.

Core Features & Use Cases

Meaningful naming and small, single-responsibility functions.
Comments that explain intent only when necessary, while the code expresses meaning.
Robust error handling and defensive programming guided by best practices.
Clear refactoring patterns aligned with SOLID principles (Single Responsibility, Open/Closed, Guard Clauses).
Team-oriented guidelines for code-review checklists and improvement workflows.

Quick Start

Audit your project against this guide and begin applying the Single Responsibility, meaningful naming, and error-handling patterns today.

Frequently Asked Questions about code-quality

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

FAQPage Schema

How do I enforce clean code guidelines consistently across a codebase?▼

You can enforce clean code guidelines by applying structured patterns for naming, small single-responsibility functions, and guard clauses consistently across all modules. This standardizes refactoring efforts and aligns teams on a shared code-quality standard.

What is the best way to refactor bloated functions using SOLID principles?▼

Refactoring bloated functions with SOLID principles involves applying Single Responsibility and Open/Closed patterns to split logic into small, focused units. This improves maintainability and ensures each function handles a clear, isolated task.

How should error handling and defensive programming be structured in software engineering?▼

Error handling and defensive programming should follow best-practice patterns that make modules robust against failures. This involves using guard clauses and clear refactoring patterns to manage exceptions consistently across the codebase.

Can this guide help structure a team-oriented code review checklist?▼

Yes, this guide provides team-oriented guidelines for code review checklists and improvement workflows. It helps reviewers check for meaningful naming, proper error handling, and adherence to SOLID principles during code reviews.

When do I need to add comments versus writing self-explanatory code?▼

Comments should explain intent only when necessary, while the code itself expresses meaning. This approach ensures maintainability by keeping comments focused on why decisions were made rather than what the code does.