specstar-clean-code

To reduce cognitive complexity and clean up dead code in Go, apply refactoring rules that enforce guard clauses, parameter cleanup, and remove unused imports, locals, and artifacts without changing the intended architecture.

Clean code refactoring simplifies branching logic and splits oversized functions by enforcing cognitive complexity limits, controlling duplication, improving naming clarity, and removing unused parameters to improve maintainability.

To check for hidden dead code and naming issues during a code review, scan for repeated literals, stale comments, and unused locals after feature additions or partial refactors to ensure merge readiness.

Yes, you can use this refactoring approach for Go services and libraries before a merge. It targets implementation and review work by removing avoidable complexity while preserving the original behavior.

The best way to remove duplicated code and confusing control flow is to apply duplication control, guard clauses, and naming clarity rules that reduce complexity while preserving the intended architecture.

You should avoid clean code refactoring when your goal is to change the intended architecture or add new features, as this approach specifically targets complexity, duplication, and dead code removal without altering behavior.