clean-code

Enforce readability standards and SOLID principles in source code.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dragoscirjan/opencode-config --skill clean-code-dragoscirjan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/clean-code
Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill clean-code-dragoscirjan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams write, review, and maintain code that is easier to read, safer to change, and less likely to accumulate technical debt.

Core Features & Use Cases

  • Clean code guidance for naming, function design, nesting, and comments.
  • Design advice for SOLID, composition, dependency injection, and practical patterns.
  • Quality tooling reminders for editorconfig, linters, duplication checks, task runners, and commit hygiene.
  • Use case: Apply it when reviewing a pull request to spot unclear abstractions, redundant logic, weak error handling, or missing project-wide quality checks.

Quick Start

Use the clean-code skill to review this module for readability, SOLID violations, error handling gaps, and missing quality tooling.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I review a pull request for clean code and readability issues?

To review a pull request for clean code, check naming conventions, function design, nesting depth, and comments. Spot unclear abstractions, redundant logic, and weak error handling to ensure maintainability and reduce technical debt.

What is the best way to enforce SOLID principles during code refactoring?

Enforcing SOLID principles during code refactoring involves applying composition, dependency injection, and practical design patterns. This ensures your source code remains modular, easier to change, and resistant to defects across application modules.

How do I set up quality tooling for code review and commit hygiene?

Set up quality tooling by integrating editorconfig, linters, jscpd for duplication checks, Semgrep, and Taskfile. Use pre-commit hooks to enforce readability standards and commit hygiene before code review.

Can I use this approach to improve error handling and defect resistance in my source code?

Yes, you can improve error handling and defect resistance by applying explicit error handling standards and universal tooling. This reduces the likelihood of accumulating technical debt and makes modules safer to change.

When do I need to apply clean code standards to architecture decisions?

Apply clean code standards to architecture decisions when you need to enforce readability, SOLID principles, and quality checks across application modules to prevent technical debt and ensure long-term maintainability.