Enforce concise coding standards using SRP, DRY, KISS, and YAGNI principles.
npx skills add https://github.com/nghialuffy/my-skills --skill clean-code-nghialuffy
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/nghialuffy/my-skills/tree/main/skills/clean-code Command: npx skills add https://github.com/nghialuffy/my-skills --skill clean-code-nghialuffy
Pragmatic coding standards ensure concise, direct, and maintainable code by avoiding over-engineering and unnecessary comments.
Refactor the current codebase to align with the pragmatic coding standards and remove redundant comments for improved clarity.
High-intent search queries and answers about installing and using this skill.
Core coding standards for maintainable code rely on SRP, DRY, KISS, and YAGNI principles to reduce over-engineering. These rules enforce concise, readable structuring and clear naming to improve software project clarity and speed up developer onboarding.
To refactor your codebase, apply pragmatic coding standards by enforcing simple function rules, clear naming conventions, and removing unnecessary comments. This process restructures code using SRP and DRY to achieve concise, direct, and highly maintainable software.
You need coding standards during code review, refactoring sessions, and onboarding to enforce a shared style. Applying principles like the Boy Scout Rule and KISS ensures new developers understand the architecture and reduces bugs through readable code.
Yes, applying clean code principles helps reduce bugs by enforcing clear naming conventions and simple function rules. Structuring code with SRP and DRY improves readability and maintainability, directly minimizing logical errors and over-engineering.
The best way to apply SRP and DRY without over-engineering is to pair them with KISS and YAGNI principles. This pragmatic coding standard approach ensures functions remain simple, direct, and free of unnecessary comments while maintaining a clean architecture.
You should remove unnecessary comments during code refactoring because pragmatic coding standards prioritize concise, readable code over redundant explanations. Clear naming conventions and simple functions make the code self-documenting, reducing bugs and improving overall maintainability.
RazisafirAnalyzes source code to flag overly complex and redundant sections requiring Python parsing.
BenavidesMichaelApply clean code principles to improve code quality in reviews, refactoring, and architecture.
ianyimiEnforce global coding style guidelines across multi-language codebases.
N4M3ZRefactor existing code to improve readability and pattern consistency.
