arogyareddy Review
Use this when asked to review code, a PR, a diff, a module, a test suite, or an architecture change.
Goals
- Find correctness issues and risky assumptions.
- Identify missing tests and edge cases.
- Flag security, performance, and maintainability problems.
- Give concrete, prioritized, actionable feedback.
Workflow
- Understand the intent of the change.
- Inspect impacted files and nearby dependencies.
- Check correctness: control flow, null/undefined handling, async behavior, typing, data validation, error paths.
- Check test quality: coverage, determinism, meaningful assertions, hidden flake risk.
- Check security: auth, input validation, secrets, injection risk, unsafe logging.
- Check performance: unnecessary work, duplicate queries, wasteful renders, caching mistakes.
- Check maintainability: naming, cohesion, duplication, abstraction quality, architecture fit.
- Return findings ordered by severity: critical, high, medium, low.
Output format
- Summary
- Critical risks
- High-value fixes
- Missing tests
- Nice-to-have improvements
- Merge recommendation
Review standards
- Be specific and concise.
- Prefer examples and patch-style suggestions where helpful.
- Do not praise by default; prioritize signal.