Ami pr self reviewer
Acts as a critical self-reviewer for your own Pull Requests (draft or published). Instead of just leaving comments, it analyzes the diff and proactively suggests and applies concrete code fixes.From its SKILL.md
npx -y skills add AnaCataVC/amiga-ia --skill ami-pr-self-reviewerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 349 tokens by cl100k_base, as published. Nobody here has run it
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
-
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.
-
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.
- Analyze the diff explicitly looking for:
-
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.
-
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 interact in the chat using the same language the user is speaking (e.g., Spanish, French, etc.).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.