task-flow-review

You can validate code changes by generating a diff against main, loading project coding standards, and analyzing the changes for architecture and convention compliance. This process runs during the code phase of a task-flow, before PRs, to ensure quality and standards compliance.

Automating code review for task-flow workflows involves detecting the execution context, generating a diff against main, and analyzing changes against loaded project standards. It automatically saves a local, timestamped review log to track iterations and ongoing improvements.

A diff-based code review compares your current branch changes with the main branch. It loads your defined coding rules, analyzes the architectural and convention differences found in the diff, and generates a comprehensive review report validating task-flow code adherence.

Yes, you can track iteration history for ongoing code reviews. The review process generates and saves a timestamped review report locally, which tracks review iterations to help you monitor ongoing improvements and standards compliance over time.

The review process detects the execution context and can operate in both task-flow and standalone contexts. It reads the diff against main, loads the required project standards, and analyzes the changes regardless of whether it runs inside a formal task-flow workflow.

You should run a code standards review during the code phase of a task-flow, immediately after implementing code, or after feature completion. Running it before PRs ensures your changes adhere to project architecture, conventions, and best practices.