Enforce clean-code discipline during writing, refactoring, and review.
npx skills add https://github.com/kartikkabadi/skills --skill clean-code-kartikkabadi
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/kartikkabadi/skills/tree/main/clean-code Command: npx skills add https://github.com/kartikkabadi/skills --skill clean-code-kartikkabadi
This Skill helps you write, refactor, and review production code so it is readable, maintainable, and easier to change without introducing regressions.
Ask for a clean-code review of the changed files and rewrite the implementation to follow naming, size, testing, and refactoring best practices.
High-intent search queries and answers about installing and using this skill.
To improve code maintainability, refactoring enforces clean-code discipline by applying intent-revealing names, splitting large functions, and removing duplication. This preserves existing behavior while reducing complexity and technical debt.
The best way to review code for clean architecture is to apply clean-code rules to naming, comments, side effects, and architectural boundaries. This ensures the implementation remains test-backed, readable, and free of unnecessary duplication.
Handling error handling and side effects during code review involves checking architectural boundaries and enforcing clean-code discipline. This process isolates side effects and ensures error handling logic remains clean, readable, and maintainable.
You can safely refactor production code by using a test-first approach with strong coverage. Reliable automated tests back fearless refactoring, ensuring you preserve behavior while reducing complexity and removing duplication.
A two-pass refactoring workflow involves first making the code work, then cleaning and simplifying it. This enforces clean-code discipline by ensuring small functions and one-level-at-a-time abstraction are applied after functionality is established.
CANTAGESTUDIOIdentify missing tests and establish a minimal safety net before refactoring.
wonjangcloud9Enforce Test-Driven Development with red-green-refactor cycles and test conventions.
CloakingGhostAutomate code review, error fixing, and structural improvements via static analysis.
camilooscargbaptistaRecommend design patterns and SOLID refactors to reduce coupling and improve modularity.
