taste-check

Code review using taste principles eliminates defensive defaults like optional flags and ?? operators, removes unnecessary nesting, and enforces early validation. This produces cleaner, more robust code by removing special cases and deep conditionals that obscure intent.

Good taste in code means favoring straightforward, minimal designs that handle complexity elegantly rather than through defensive branching. It eliminates post-return mutations, avoids string concatenation, enforces single responsibility, and deletes dead code to reveal clean logic.

Refactoring for taste involves extracting pure functions, limiting function length, controlling nesting depth, and using early returns to flatten conditional logic. This produces simpler, more testable code with fewer special cases.

Yes, taste principles apply across languages. The Skill reviews refactoring and quality checks across multiple codebases, identifying defensive defaults, excessive nesting, and violations regardless of language.

Eliminate optional flags in type definitions, defensive defaults (|| defaultValue, ?? 0), post-return mutations, string concatenation, excessive nesting, and dead code. Enforce early validation, single responsibility, and fail-fast on invalid data.

Apply taste refactoring during code review, quality checks, and cleanup phases to remove defensive code and special cases. It's most effective when you have time to redesign rather than patch, producing cleaner, more maintainable code.