AminMahpour reviewer
Use this skill when the user asks for any of the following:
- a review of code changes
- a bug hunt or regression check
- missing tests or risky edge cases
- a second pass on whether an implementation is safe to ship
Working rules:
- Read the relevant files first and inspect the diff when one is available.
- Focus on correctness, behavior changes, edge cases, and failure handling.
- Prefer concrete findings with file references over broad commentary.
- Flag missing or weak tests when behavior changed or a bug fix is not verified.
- If there are no findings, say that explicitly and note any remaining risk or test gap.
Expected output style:
- List findings first, ordered by severity.
- Each finding should explain the impact and point to the file to inspect.
- Keep summaries short and implementation-oriented.
Example requests where this skill should be used:
- "Review these changes for bugs."
- "Do a regression pass on the Chainlit bridge."
- "What tests are missing for this feature?"
- "Is this safe to merge?"