Apply clean-code principles to naming, structure, and testing.
npx skills add https://github.com/dzackgarza/ai --skill clean-code-dzackgarza
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/dzackgarza/ai/tree/main/opencode/skills/clean-code Command: npx skills add https://github.com/dzackgarza/ai --skill clean-code-dzackgarza
Clean code makes software easier to read, understand, and modify. It reduces bugs by clarifying intent, improving naming, structure, and testing practices.
Refactor a small function to improve naming and reduce complexity, then add a focused unit test following the chapter guidance.
High-intent search queries and answers about installing and using this skill.
To apply clean code principles during refactoring, improve naming to be intent-revealing, reduce function complexity by keeping functions small and cohesive, and add focused unit tests. This clarifies purpose and reduces bugs by making code easier to understand and modify.
The Single Responsibility Principle (SRP) ensures classes and functions have one reason to change, keeping them small and well-scoped. Applying SRP during refactoring improves code maintainability by limiting side effects and clarifying structural intent.
Writing meaningful names involves using expressive, intent-revealing identifiers that communicate purpose. This clean code practice makes software easier to read and modify by clarifying intent, which is especially useful during code reviews and onboarding.
Yes, clean code guidelines are applicable to software projects of any size where code clarity matters. They enforce meaningful names, limited side effects, and domain-driven test coverage, making them highly effective during code reviews and onboarding.
The best way to structure unit tests is by using clear, domain-driven test coverage that aligns with small functions and minimal side effects. This approach ensures tests are focused and maintainable, directly reflecting the business logic and intent-revealing names.
Aggressive refactoring to enforce clean code standards should be approached cautiously when it risks expanding side effects or breaking existing domain-driven test coverage. Limit changes to small, cohesive function modifications to ensure safe, maintainable evolution.
BerryKuipersRecord code quality metrics before refactoring into a timestamped JSON baseline.
thec3ukEnforce unit test quality and conformance to coding standards.
damacusIdentify Sandi Metz design violations in Ruby code and report structured feedback.
TheBushidoCollectiveEnforce component orthogonality to reduce ripple effects in software systems.
