star-code-reviewer

To audit source code for adherence to project conventions, run a static analysis pass across your defined project scope, such as git diffs, specific plan modules, or entire codebases, to identify blockers, major issues, and minor style deviations.

Verifying code implementations match the tasks and done-criteria defined in project plans requires a plan conformance check, validating deliverables through evidence-backed reporting to ensure alignment with your established project scope.

Yes, you can automatically apply mechanical, behavior-preserving fixes like docstring updates and unused import removal through a safe, interactive pass designed to update code without altering its functional logic.

Static analysis checks code against a six-dimension rubric including docstrings, naming, simplicity, and project-specific conventions by scanning the codebase and generating evidence-backed reports that highlight deviations and blockers.

Yes, the code review process operates across defined project scopes including git diffs, specific plan modules, or entire codebases, allowing you to target exactly which sections of the project receive the convention audit.

Static analysis for convention auditing in a research workflow is limited to identifying mechanical deviations and plan conformance issues; it cannot evaluate complex runtime logic or subjective architectural decisions outside its six-dimension rubric.