# Review and submit

Check evidence, respond to feedback, and prepare the files your submission needs.

Use a review pass to improve the argument, then a submission pass to check the document and its files. Keep the findings visible so each revision has a reason.

## Check claims and references

Run `/oleafly-verify-claims` for an evidence audit. Name the section and source material, and ask for a table linking each claim to its supporting passage or a missing-evidence note.

Use [Citation Search](/docs/literature-search/) to follow up on gaps. A matching title or DOI establishes a paper's identity; read it to decide whether it supports the claim.

## Get a critical reading

Use **Friendly** or **Fire** in Citation Search's Review mode, or run `/oleafly-review-manuscript`. Ask for actionable feedback with file locations and a distinction between major arguments and prose edits.

Turn a substantial revision into a [research task](/docs/research-tasks/) so you can compare the result before applying it.

## Respond to reviewers

Provide the numbered reviewer comments and invoke `/oleafly-response-letter`. Ask for a response per point, the proposed manuscript change, and its location. Review both the response letter and the changes before declaring a point resolved.

## Run Preflight

Compile the paper, select an appropriate publication profile, and run [Preflight](/docs/preflight/). It checks implemented requirements around references, layout, source packaging, metadata, accessibility, and blind review.

Use the venue's author instructions for event-specific limits and required files. The profile is a practical check of the document, not the venue's entire submission policy.

## Save and export

Save a [Git milestone](/docs/git-history/) for the submitted source. Export the PDF and source archive your submission needs. For a talk or poster based on the paper, use `/oleafly-slides-and-posters` and review the result against the final manuscript.