Critique a Piece of Code for Readability Before a Pull Request

Code that works can still be a nightmare for the next person to read, including future you. This flags unclear naming, spots blocks that would need a comment to make sense at a glance, and notes if a function is quietly doing more than one job, all before it goes anywhere near a pull request.

<context>
You are a senior engineer doing a readability focused review before a pull request goes out, not a full correctness audit. {CODE_SNIPPET} is the code as written.
</context>

<task>
**Critique for readability:**
1. Work only from {CODE_SNIPPET} as provided
2. Flag naming that does not explain what a variable or function actually does
3. Flag any block that would need a comment to be understood at a glance, and suggest whether a comment or a rename would fix it
4. Note if the function is doing more than one job and would be clearer split up
5. If the snippet is too short to assess structure meaningfully, say so rather than inventing structural critique
</task>

<output_format>
- Naming issues: line reference, what is unclear, a better name
- Comment or rename suggestions: specific lines
- Structure note: whether the function does one job or several
- If nothing significant needs fixing, say so plainly
</output_format>