Guide code changes toward concise, maintainable implementations with dependency impact checks.
npx skills add https://github.com/capaas2/Site-teste --skill clean-code-capaas2
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/capaas2/Site-teste/tree/main/.agent/skills/clean-code Command: npx skills add https://github.com/capaas2/Site-teste --skill clean-code-capaas2
This Skill helps developers make safer, simpler code changes without over-engineering, unnecessary comments, or broken dependencies.
Use the clean-code skill to review this change for simplicity, dependency impact, and whether all affected files and tests are updated.
High-intent search queries and answers about installing and using this skill.
To refactor code without breaking dependencies, you must check imports, dependents, tests, and shared components before editing. This ensures changes remain dependency-safe and prevents leaving the project in a broken state during software engineering tasks.
Clean code applies pragmatic standards like SRP, DRY, KISS, and YAGNI to bug fixes, ensuring implementations stay concise and maintainable. It reinforces validation checks and completion discipline to ship reliable software engineering changes.
Adding a feature without over-engineering requires applying clean architecture principles and avoiding unnecessary comments. You must perform validation checks and update all affected files to ensure the feature addition is complete and maintainable.
Yes, this approach works for dependency-safe file edits by enforcing strong change-impact awareness. It requires checking imports and shared components before editing, ensuring the codebase maintains integrity during refactoring or feature additions.
The best way to review code changes for maintainability is to apply SRP, DRY, KISS, and YAGNI principles while verifying that all affected files and tests are updated. This reinforces self-checks to prevent broken project states.
You should avoid over-engineering in software engineering tasks when concise, maintainable implementations are sufficient. Applying pragmatic standards like KISS and YAGNI prevents unnecessary complexity during bug fixes and refactoring.
ElliotJLTTraces callers and dependents before editing shared code to map impact.
OpenRaiserFix LaTeX Overfull \hbox defects with minimal .tex source edits.
jonnathan-lsApply clean-code principles to code reviews and refactoring.
ArabelaTsoAnalyze Python codebases to identify component boundaries and detect architectural violations.
