skills.rest
onesyntax
onesyntaxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

clean-code-review

Assess code quality across naming, functions, classes, and architecture.

5|Updated Jan 31, 2026
Search Tags:#architecture#quality#SOLID#code-review#naming#clean-code#Uncle Bob
One-click install
npx skills add https://github.com/onesyntax/skills --skill clean-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code-review
Source: https://github.com/onesyntax/skills/tree/main/skills/clean-code-review
Command: npx skills add https://github.com/onesyntax/skills --skill clean-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable Clean Code review workflow based on Uncle Bob's principles, ensuring readability, maintainability, and correctness before merging or delivering software.

Core Features & Use Cases

  • Comprehensive naming checks and consistent terminology across the codebase using a formal /naming workflow.
  • Function-level analysis emphasizing small, single-responsibility functions and clear abstractions.
  • Class and architecture evaluation (SRP, cohesion, coupling, and SOLID adherence) to guard against leakage of concerns.
  • Pattern usage assessment ensuring appropriate abstraction, proper layering, and inward dependencies.
  • Error handling, comments, formatting, and test quality evaluations to improve code health.
  • Use-case: run this review on a feature branch to catch critical issues before code is merged, especially after refactors or TDD cycles.

Quick Start

Activate the skill on your codebase after completing a feature. Provide the latest changes (diff or context) to the skill and request a full Clean Code review.

Frequently Asked Questions about clean-code-review

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

FAQPage Schema
How do I perform a clean code review on a feature branch before merging?▼

A clean code review assesses naming, functions, classes, and architecture using Uncle Bob's principles. It enforces structured checks across SOLID adherence and test quality to ensure software readability and maintainability.

Can I use this to check SOLID architecture and single responsibility in refactored code?▼

Yes, you can use it to check SOLID architecture and SRP in refactored code. It evaluates class cohesion, coupling, inward dependencies, and pattern usage to guard against leakage of concerns after refactors.

What's the best way to enforce consistent naming and small functions in my codebase?▼

To enforce consistent naming and small functions, trigger the formal naming and function-level analysis workflows. They evaluate single-responsibility functions and consistent terminology to improve overall code health.

Does this clean code review evaluate error handling, comments, and test quality?▼

Yes, this clean code review evaluates error handling, comments, formatting, and test quality. These structured checks assess code health and output prioritized actionable feedback for developers to address.

When should I run a structured code-quality assessment on my software project?▼

Run a structured code-quality assessment after completing a feature, especially following refactors or TDD cycles. It ensures correctness and readiness for review before you merge or deliver the software.

Related Skills

Explore More Software Engineering Skills→
haidonglethqbhaidonglethqb

ck:watzup

Summarize current branch commits and diffs for code review.

Community
Intermediate
PacificStudioPacificStudio
264

review-code

Review code changes for risks with prioritized findings and file references.

Official
Intermediate
hatlesswizardhatlesswizard
4

clean-code-ch10-classes

Detect class design defects like SRP violations and low cohesion.

Community
Intermediate
dodygdodyg

dotnet-editorconfig

Generate .editorconfig files to enforce .NET code style and analysis rules.

Community
Intermediate