clean-code

Enforces pragmatic coding standards for concise, direct, and maintainable code generation.

2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill clean-code-shubh2310-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/Shubh2310-developer/ENGUNITYCORE/tree/main/.claude/skills/clean-code
Command: npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill clean-code-shubh2310-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code often suffers from over-engineering, excessive comments, deep nesting, and bloated functions. This Skill enforces pragmatic coding standards so generated code stays concise, readable, and free of unnecessary abstractions. ## Core Features & Use Cases - Coding Standards Enforcement: Applies SRP, DRY, KISS, YAGNI, and Boy Scout principles with concrete naming, function size, and structure rules. - Anti-Pattern Detection: Flags common mistakes like god functions, magic numbers, deep nesting, and unnecessary helper files, with direct fixes. - Dependency-Aware Editing: Requires checking imports, dependents, and test coverage before modifying any file, preventing broken references. - Use Case: When asking an AI agent to add a feature or fix a bug, this Skill ensures it writes the code directly, edits all dependent files in the same task, and runs a mandatory self-check before declaring completion. ## Quick Start Apply the clean-code standards to refactor this module and fix any broken imports in dependent files.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I enforce clean code standards in AI-generated code?

Load coding standards as explicit rules covering naming, function size, and structure before generation. This Skill applies SRP, DRY, KISS, and YAGNI principles with concrete limits like 20-line functions and maximum 3 arguments.

What are the most common AI coding anti-patterns to avoid?

Common anti-patterns include commenting every line, creating helpers for one-liners, god functions, deep nesting, and magic numbers. Each should be replaced with self-documenting names, inlined code, guard clauses, and named constants.

How do I prevent broken imports when editing shared files?

Before editing any file, identify what imports it, what it imports, and which tests cover it. Edit the file and all dependent files in the same task so no broken imports or missing updates remain.

When should I not add comments to code?

Avoid comments that restate what the code already expresses. If a comment is needed to explain a name, rename the variable or function instead so the code self-documents.

What is the maximum recommended function length in clean code?

Functions should be at most 20 lines, ideally 5 to 10, doing one thing at one level of abstraction. Longer functions should be split by responsibility into smaller composed units.