frontend-code-review

Review frontend code changes by applying a structured, checklist-based approach to staged or changed files. This process flags quality, performance, and maintainability issues, outputting findings in a standardized format with urgency tags for fast triage before commit submission.

A checklist-based frontend code review systematically assesses code changes against living guidelines and best practices. It inspects specific files or pending changes to enforce quality and maintainability standards, reporting violations and tagging their urgency to streamline the triage process.

Yes, you can target specific file(s) for a frontend code quality check by naming them directly. The review will inspect only the requested files, apply the checklist to find quality and performance issues, and report the relevant findings with appropriate urgency tags.

Yes, the frontend review process supports linting and maintainability checks by referencing living guidelines to apply up-to-date best practices. It systematically flags checklist violations related to code quality, maintainability, and performance during the file inspection.

The best way to triage frontend code review findings is by using a standardized output format with urgency tagging. This approach enforces the prioritization of correctness, performance, and maintainability issues flagged during the checklist-based review of pending changes.