Pre-Push Review and Autofix

Done means you can run pre-push AI review and manage autofix branches safely.

AI review adds signal in the PR flow, but the human still owns the merge.

Use Cursor review commands and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. autofix when you want review before pushing or want a reviewed finding fixed by a cloud agent. Keep the boundary narrow.

Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.

Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.

Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.

1. 1Run the relevant review command before pushing risky changes.
2. 2Inspect findings and decide which ones need action.
3. 3Use autofix for bounded, reproducible issues.
4. 4Review the autofix branch like any other agent-generated PR.

The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.

Verification decides the next move.

Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.