implementation-review-before-commit

Review staged git changes for code quality by running a pre-commit workflow that collects the diff, checks for unnecessary abstractions and deep nesting, and outputs a PASS/WARN/FAIL assessment with actionable improvements.

Yes, you can check staged code for unnecessary complexity during pull requests by applying a review process that reconstructs commit intent from the diff, evaluates simplicity, and traces requirement alignment to ensure maintainability.

The best way to ensure maintainability in a pre-commit code review is to apply a checklist workflow that evaluates pattern consistency and low complexity, then reports a clear PASS/WARN/FAIL result with traceability.

Yes, the code review workflow works with local commits and pull requests by applying a consistent process to staged changes, evaluating requirement alignment, and reporting recommended improvements before finalizing the commit.

A pre-commit review process prevents unnecessary abstractions and misaligned requirements from entering the codebase by evaluating staged changes and generating a clear assessment before the commit is finalized.

The staged changes review reconstructs intent from the diff and traces requirements, but it relies on the context of the current staged files, meaning its PASS/WARN/FAIL assessment is limited to the scope of the immediate changes.