pr-reviewlisted

# PR Review ## Find the PR ```bash gh pr list --head $(git branch --show-current) --repo Significant-Gravitas/AutoGPT gh pr view {N} ``` ## Read the PR description Before reading code, understand the **why**, **what**, and **how** from the PR description: ```bash gh pr view {N} --json body --jq '.body' ``` Every PR should have a Why / What / How structure. If any of these are missing, note it as feedback. ## Read the diff ```bash gh pr diff {N} ``` ## Fetch existing review comments Before posting anything, fetch existing inline comments to avoid duplicates: ```bash gh api repos/Significant-Gravitas/AutoGPT/pulls/{N}/comments --paginate gh api repos/Significant-Gravitas/AutoGPT/pulls/{N}/reviews ``` ## What to check **Description quality:** Does the PR description cover Why (motivation/problem), What (summary of changes), and How (approach/implementation details)? If any are missing, request them — you can't judge the approach without understanding the problem and intent. **Correctness:** logic errors, off-by-one, missing edge cases, race conditions (TOCTOU in file access, credit charging), error handling gaps, async correctness (missing `await`, unclosed resources). **Security:** input validation at boundaries, no injection (command, XSS, SQL), secrets not logged, file paths sanitized (`os.path.basename()` in error messages). **Code quality:** apply rules from backend/frontend CLAUDE.md files. **Architecture:** DRY, single responsibility, modular functions. `