reviewing-faber-tasks

To review code diffs from automated development tasks, inspect the changes against the base branch to determine whether to merge, mark as done, continue development, or delete the unsatisfactory work.

The best way to route completed Faber tasks is by assessing the code diff to decide the next action: merging successful changes, marking exploratory tasks as done, continuing with new directions, or deleting unsatisfactory work.

Handling merge conflicts from automated code review workflows involves following provided conflict recovery guidance to resolve issues before deciding whether to merge the task or continue development with new directions.

You should delete unsatisfactory work from an automated development task when the code diff assessment shows the changes do not meet requirements and cannot be salvaged by continuing development with new directions.

Yes, you can mark exploratory development tasks as done without merging the code by assessing the task output and routing it as complete based on the structured review process.

No, the Faber task review process does not require any specific dependencies, relying only on scripts and references to inspect code diffs and route the completed tasks appropriately.