clean-code

Enforce naming conventions, folder structure, and Task-ID comments across codebases.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/AreebaZafarChohan/todo-evaluation --skill clean-code-areebazafarchohan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/AreebaZafarChohan/todo-evaluation/tree/main/.claude/skills/clean-code
Command: npx skills add https://github.com/AreebaZafarChohan/todo-evaluation --skill clean-code-areebazafarchohan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure code is readable, maintainable, and traceable to approved tasks. This skill enforces clean code principles that enable team collaboration, code review, and long-term system health.

Core Features & Use Cases

  • Readable by humans: intent is obvious without comments
  • Maintainable: easy to modify without breaking things
  • Traceable: every change links to an approved task
  • Focused: each function does one thing well
  • Simple: avoid unnecessary complexity

Quick Start

Organize your codebase according to the naming conventions, folder structure, and Task-ID rules described in this guide.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I enforce naming conventions and folder structure across a codebase?

Enforce naming conventions and folder structure by applying clean code guidelines that codify organizational rules across modules. This ensures codebase readability and maintainability, making intent obvious without relying on extra comments.

What is code traceability and how does it link changes to approved tasks?

Code traceability links every code modification to an approved task using mandatory Task-ID comments. This mechanism enforces disciplined refactoring and ensures all changes are trackable for team collaboration and code review.

How do I refactor code to make it readable and maintainable for team collaboration?

Refactor code for readability and maintainability by enforcing focused functions that perform single tasks and avoiding unnecessary complexity. This approach enables long-term system health and simplifies team collaboration during code reviews.

Can I apply clean code rules to software projects of any size?

Yes, you can apply clean code rules to software projects of any size. The guidelines scale across small and large codebases, enforcing consistent code organization, naming conventions, and traceability requirements throughout the system.

What's the best way to document code structure and avoid unnecessary complexity?

Document code structure and avoid unnecessary complexity by adhering to clean code principles that make function intent obvious without comments. This involves organizing folders by convention and ensuring each function does one thing well.

When do I need mandatory Task-ID comments for code refactoring?

You need mandatory Task-ID comments for code refactoring whenever a change must be traceable to an approved task. This requirement ensures disciplined modifications and maintains historical context for long-term system health.