code-review-kiss-detector

Detect KISS principle violations in codebases and suggest refactoring recommendations.

21|8|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/speednet-software/speedwave --skill code-review-kiss-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-kiss-detector
Source: https://github.com/speednet-software/speedwave/tree/main/.claude/skills/code-review-kiss-detector
Command: npx skills add https://github.com/speednet-software/speedwave --skill code-review-kiss-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and document violations of the KISS principle (Keep It Simple, Stupid) in software projects to improve readability, maintainability, and long-term viability.

Core Features & Use Cases

  • Detect and categorize common KISS violations: Over-Abstraction, Premature Generalization, Over-Engineering, Unnecessary Indirection, and Convoluted Logic.
  • Provide actionable refactoring recommendations with clear trade-offs and maintainability impact.
  • Support code-review workflows by summarizing issues and suggesting concrete next steps.

Quick Start

Run a code review to identify KISS violations and present actionable simplifications.

Frequently Asked Questions about code-review-kiss-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find over-engineering and KISS violations in my codebase?

To find KISS violations, analyze codebase structure and logic to surface over-abstraction, premature generalization, and unnecessary indirection. The review evaluates abstraction depth and decision paths to pinpoint exact locations of unnecessary complexity.

What is premature generalization and how do I detect it during a code review?

Premature generalization is adding speculative flexibility before requirements demand it. Detect it by evaluating abstraction depth and data flow to identify unnecessary indirection and convoluted logic, categorizing these as concrete KISS violations.

Can I run a KISS code review across different programming languages?

Yes, you can apply KISS detection across software projects regardless of language. The analysis focuses on structural patterns like over-engineering and unnecessary indirection rather than language-specific syntax.

How do I refactor unnecessary abstraction to improve code maintainability?

Refactor unnecessary abstraction by applying actionable recommendations that reduce indirection and simplify decision paths. This improves readability and long-term viability by presenting clear trade-offs and maintainability impacts for each change.

What is the best way to identify convoluted logic in software projects?

The best way to identify convoluted logic is to analyze decision paths and data flow within the codebase. This surfaces specific issues with severity ratings and concrete refactoring steps to simplify the code.

When should I not use KISS principle refactoring recommendations?

Avoid KISS refactoring when abstractions are explicitly required to handle verified complexity or domain rules. The tool targets unnecessary indirection and premature generalization, meaning justified architectural depth should remain untouched.