Analyze code implementations for over-engineering against project conventions.
npx skills add https://github.com/CivicActions/ai-runbook-jh --skill kiss-civicactions
Please help me install this Agent Skill. Skill: kiss Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/kiss Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill kiss-civicactions
This Skill identifies unnecessary complexity, premature abstractions, and over-engineered solutions in your codebase, ensuring your implementation remains maintainable and lean.
Use the kiss skill to review the provided code implementation for unnecessary complexity and suggest a simpler approach.
High-intent search queries and answers about installing and using this skill.
To identify over-engineering in your codebase, analyze code implementations against project-specific stack conventions and universal simplicity principles to detect premature abstractions and single-use abstractions.
Common signals of premature abstractions in software architecture include single-use abstractions, redundant custom utilities, and premature generalizations that deviate from framework-native alternatives and standard library capabilities.
Review code for unnecessary complexity during peer reviews by evaluating the provided code snippet against the project contract to ensure the implementation remains maintainable, lean, and appropriately simple.
Yes, you need a project contract and the code snippet to evaluate code simplicity and maintainability, as the assessment requires comparing implementations against project-specific stack conventions and framework-native alternatives.
You should avoid custom utilities for software architecture when they act as redundant single-use abstractions, and instead use framework-native alternatives or standard library capabilities to keep solutions maintainable and efficient.
The best way to eliminate over-engineering in a custom service layer is to critique it against project conventions to receive a recommendation for a simpler, more direct implementation using standard library capabilities.
SebKayAudit codebases for non-idiomatic language and framework usage.
Tyler-R-KendrickAudit a codebase and rank simplification and code removal opportunities.
JuniYadiAssess software proposals against clean architecture and maintainability criteria.
bytetalentApply the rule of three to reuse existing code patterns.
