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. 3. **Concrete Code Suggestions:** - Instead of leaving abstract comments (e.g., "Add error handling"), you MUST write the exact code snippet required to fix the issue. - Present your findings as a numbered list. For each flaw, provide the proposed code modification. 4. **Proactive Implementation:** - Ask the user: "Would you like me to apply these fixes directly to the files?" - If the user approves, use your file editing tools to apply the exact fixes locally. - Once applied, advise the user to amend their commit or push the new changes to their branch. --- **Language Rule:** Although your code and commits MUST be in English, you MUST communicate and inter