code-quality-check

To check code quality before merging, apply a review checklist to added or modified files to identify and fix linting, naming, complexity, and duplication issues. This pre-merge pass catches quality regressions that automated tests may miss.

A pre-merge code review checklist includes verifying linting and formatting, naming conventions, complexity, duplication, dead code removal, and edge case handling. It targets only newly added or modified source code without refactoring unrelated code.

To detect duplicated functions and dead code in modified files, run a complexity and duplication detection pass on the changed source. This process identifies long or duplicated functions and suggests extraction or reuse to remove dead code.

Yes, this code quality check works across both frontend and backend repositories. It applies to post-implementation reviews, pre-merge checks, and CI workflows to ensure newly added or modified code meets project expectations.

Yes, you can enforce naming conventions and linting in a CI workflow by running configured linters and formatters on added or modified files. The process fixes violations and verifies variables, functions, and classes follow project conventions.