#043Tutorial1 min

Review and approve a fix proposal

Read files, reasoning, validations and limits before an explicit human approval.

Hackaiz team · updated 18/11/2026

Illustration: two developers review a change before approving it.
Illustration: two developers review a change before approving it. Illustrative photo, not a screenshot.

01Review before approving

Approval is a human decision: no one else, neither Hackaiz nor an assistant, makes it for you. Read the proposal as you would read a colleague’s.

  1. 1Do the touched files match the finding?
  2. 2Is the diff limited to what is needed?
  3. 3Did the listed validations pass?
  4. 4Are the stated limits acceptable to you?

02Approve

If the proposal suits you, click Approve. Hackaiz rechecks GitHub access, then proposes the change on a dedicated branch of your repository. If access changed, nothing is written and a message tells you.

03Decline or ask for better

If the proposal does not suit you, do not approve it. You can fix it yourself from the explanation, or prepare a new proposal. A write with an uncertain outcome is never retried automatically.

04After approval

On GitHub, review the change request, run your tests and merge yourself if everything is right. Then re-run the analysis: “applied” is not “verified”.

Tip: On a phone, the diff wraps lines; for a large change, prefer a computer.

Frequently asked questions

Take the next step

Was this article helpful?

Related articles