Enforce pragmatic clean-code conventions for readable, maintainable source code.
npx skills add https://github.com/miptah21/skills --skill clean-code-miptah21
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/miptah21/skills/tree/main/.agents/skills/clean-code Command: npx skills add https://github.com/miptah21/skills --skill clean-code-miptah21
It reduces bugs and maintenance cost by enforcing pragmatic coding standards for clarity, small functions, and minimal unnecessary complexity—especially important when working with AI-generated code.
Use the clean-code skill to update the target file while following the “Before Editing ANY File (THINK FIRST!)” checklist, then run the centralized compliance runner to confirm the change passes validation.
High-intent search queries and answers about installing and using this skill.
To enforce clean code conventions during refactoring, apply pragmatic rules for naming, small function sizes, and guard clauses to minimize common AI code smells and over-engineering. This ensures readable, maintainable source.
The safe editing workflow for shared codebase files requires a pre-change checklist to analyze imports, dependencies, and tests before modifying. This dependency-aware edit plan prevents breaking existing functionality.
Applying SRP, DRY, and KISS principles without over-engineering requires writing concise, direct code with intention-revealing names and flat logic over deeply nested structures. This minimizes unnecessary complexity.
Yes, the clean-code skill provides centralized compliance scripts to run lint, type safety, and i18n validation. Running these scripts after changes confirms your code passes required quality checks.
You should use guard clauses to avoid deeply nested logic when implementing features or fixing bugs, favoring flat over deeply nested structures. This produces concise, direct code that stays readable.
The best way to prepare changes to shared codebases is following a dependency and test-aware edit plan, applying clean coding rules, then running compliance scripts for validation. This ensures maintainable source.
vab1997Interrogate plans through structured one-question-at-a-time decision-tree exploration.
jrmatherlyRun backend tests, lint, and frontend type checks before commits.
grasbergEnforces SRP, DRY, KISS coding standards across AI projects via linting and refactoring.
Next-ofkinAnalyze code for smells and SOLID violations, then generate a prioritized refactoring plan.
