skills.rest
bibekshrestha77
bibekshrestha77COMMUNITY
Explore all skills by this author →
GitHub

clean-code

Enforce SRP, DRY, KISS, and YAGNI coding standards for maintainable code.

Updated Aug 23, 2026
Search Tags:#refactoring#code-quality#coding-standards#naming-conventions#software-engineering#clean-code
One-click install
npx skills add https://github.com/bibekshrestha77/VehicleRent --skill clean-code-bibekshrestha77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/bibekshrestha77/VehicleRent/tree/main/VehicleRentingSystem/.agent/skills/clean-code
Command: npx skills add https://github.com/bibekshrestha77/VehicleRent --skill clean-code-bibekshrestha77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic, consistent coding guidelines reduce ambiguity and over-engineering, helping teams write clear, maintainable code.

Core Features & Use Cases

  • Enforce SRP, DRY, KISS, and YAGNI to guide function and class design.
  • Provide naming conventions, minimal nesting, guard clauses, and avoidance of unnecessary comments.
  • Use Case: A developer refactors a module to remove duplication and improve readability while preserving behavior.

Quick Start

Follow the documented rules to review and refactor a module so it adheres to SRP, DRY, and KISS.

Frequently Asked Questions about clean-code

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

FAQPage Schema
What are clean code standards for reducing ambiguity and over-engineering in software projects?▼

Clean code standards reduce ambiguity by enforcing pragmatic rules for SRP, DRY, KISS, and YAGNI to guide developers in writing concise, readable, and maintainable software.

How do I refactor a module to remove duplication and improve readability?▼

Refactor a module by applying documented coding guidelines to enforce minimal nesting, guard clauses, and DRY principles, which removes duplication while preserving behavior and improving readability.

What naming conventions and structural rules should I apply for maintainable code?▼

Maintainable code requires specific naming conventions, minimal nesting, and guard clauses, alongside guidelines to avoid unnecessary comments, ensuring a scalable and testable coding culture.

When should I apply the KISS and YAGNI principles during software development?▼

Apply the KISS and YAGNI principles during function and class design to prevent over-engineering, keeping code concise, readable, and maintainable across typical codebases.

Can these coding standards be used to review an existing codebase?▼

Yes, you can use these coding standards to review and refactor an existing module so it adheres to SRP, DRY, and KISS, establishing a scalable and testable coding culture.

Related Skills

Explore More Software Engineering Skills→
jankneumannjankneumann
4

tech-debt-analysis

Analyze codebase complexity, coupling, duplication, and import issues to generate markdown and JSON reports.

Community
Advanced
SimpleEveSimpleEve
30

eo-test

Validate code changes with automated unit and integration tests and generate a test.md report.

Community
Intermediate
igbuendigbuend
8

semgrep

Automates static code analysis with Semgrep to detect vulnerabilities and anti-patterns.

Community
Intermediate
cwilliams5cwilliams5
1

review-outside-box

Analyzes entire codebases for systemic performance, bug, and anti-pattern issues.

Community
Advanced