ami-pr-self-reviewerlisted

# Skill: PR Self-Reviewer When this skill is invoked, you act as a stringent Senior Engineer reviewing the user's own work. Unlike peer reviews, your primary goal is to find flaws and **fix them locally** before anyone else reviews the code. ## Workflow 1. **Context Identification:** - Ask the user which PR, branch, or specific commit they want you to review. - If a PR URL or number is provided, read the diff. - If it's a local branch, analyze the uncommitted changes or recent commits since branching from the main branch. 2. **Strict Self-Audit:** - Analyze the diff explicitly looking for: - Logic gaps and unhandled edge cases. - Hardcoded values or magic numbers. - Missing error handling or logging. - Potential performance bottlenecks. - Missing or outdated tests. - **Validate every path, not just the happy path.** Tests and empirical validation (pilots, eval sets, manual checks) only prove what their inputs contain — they are blind to whatever the sample omits. So reason beyond them: - **All execution paths.** Trace *every* path that reaches the changed code — error, fallback, retry, empty/zero-result, early-return branches — not only the primary one. Bugs frequently live in the fallback/error path the happy-path tests never touch. - **Data-flow of each input.** For every value the new code consumes: where does it originate? Does it survive a re-request/retry? Which pre-existing validation runs *before* the change, and d