code-review

Automated code review in CI workflows identifies and fixes mechanical issues in modified files after tests pass, then generates a review report. It applies safety checks before applying auto-fixes and proposes semantic improvements requiring user confirmation.

Auto-fixing linting and code quality issues in TypeScript projects involves scanning modified files against project standards, applying mechanical non-semantic changes automatically, and suggesting structural improvements that require explicit confirmation before integration.

Yes, automated code review works with JavaScript and TypeScript files modified during a run. It surfaces changes from files_created and files_modified arrays, ensuring coding standards from the .specs-fire/standards directory are respected across projects.

You can enforce project coding standards automatically by running a post-run review that checks modified files against defined specifications. It auto-fixes trivial mechanical deviations and generates a report detailing suggested improvements for the parent workflow.

Auto-fixing code quality issues is limited to mechanical, non-semantic changes to guarantee safety. Improvements that alter code semantics or logic are not applied automatically; they are proposed as suggestions requiring explicit user confirmation before execution.

Running code review on files created or modified by CI pipeline runs requires scanning the files_created and files_modified outputs. The review process checks for standard adherence, applies safe auto-fixes, and returns a comprehensive review report.