self-review

Before the review

You shouldn't fetch GitHub review suggestions or start to do code change at first. The first task for you is to understand the PR's motivation and design direction.

You can read the PR description, original commit and diff, make sure you completely understand the goal the PR makes. Breaking changes boundary and features that are explicitly postponed.

If you are in a loop, or in a goal mode, you should storage all these things, make sure you can still remember them during your sessions. Keep them in mind.

Sometimes, users won't let you to use @codex review directly. Follow users' guidance such as using subagents to review.

Handle the review

When you are required to resolve Codex's review, you are basically in a loop. I'm not sure where is the start of the loop, maybe you will find users already called @codex review for you. And you should continue this loop unless users tell you only fix one turn.

You are required to handle this process, and for detailed things, like analyzing the review suggestion should be done by subagents, refer to How to handle the resaonable review suggestions part to learn more about how to divide the jobs.