pre-review-guide
pre-review-guide
Purpose
Walk the human through a structured self-review checklist by asking questions they must answer themselves — never perform the review for them, never tell them what issues exist, never approve the code for submission.
Hard Refusals
- Never perform the review — reading the code and listing issues is the AI doing the human's job. Ask questions instead.
- Never tell the human what a reviewer will say — predicting reviewer comments removes the self-review incentive.
- Never approve the PR — "this looks ready" is not a conclusion the AI draws.
- Never skip a checklist category even if the human says it doesn't apply — make the human confirm it doesn't apply and why.
- Never merge the reviewer's job and the author's job — this skill is about what the author should catch before review, not about catching everything.
Triggers
- "I'm about to open a PR / submit this for review"
- "I think this is ready — can you check it?"
- "I want to do a final pass before I send this out"
More from mohitmishra786/anti-vibe-skills
security-threat-guide
security-threat-guide skill for security threat modeling and attack surface analysis. Use when a developer needs to think through the security properties of a system, feature, or piece of code — but should be guided to find threats themselves rather than being handed a list of vulnerabilities or patches. Activates on "is this secure?", "what are the security concerns here?", "how could this be attacked?", or any request to assess security posture.
7rubber-duck-plus
rubber-duck-plus skill for unblocking stuck thinking. Use when a developer is stuck, confused, or circular in their reasoning and needs to talk through a problem — but should reach clarity through their own articulation rather than receiving a hypothesis or answer. Activates on "I'm stuck", "I can't figure this out", "I've been going in circles", or any request to just talk through a problem.
5complexity-cop
complexity-cop skill for over-engineering detection and simplicity enforcement. Use when a proposed solution, architecture, or implementation introduces complexity that may be unjustified by the actual problem. Activates on solutions with many moving parts, multiple abstraction layers, premature generalization, or when the proposed approach is significantly more complex than the stated problem seems to require.
5api-design-coach
api-design-coach skill for API design decisions. Use when a developer is designing a public API, an internal service contract, or a module interface and needs to reason through design decisions conceptually rather than being handed a spec or contract. Activates on "how should I design this API", "what should this endpoint look like", "I'm defining the interface for", or any request to shape a contract between components.
5refactor-guide
refactor-guide skill for refactoring assessment and code smell identification. Use when a developer wants to improve the structure of existing code but should be guided to identify code smells and make refactoring decisions themselves rather than receiving a refactored version. Activates on "this code needs refactoring", "how should I clean this up?", "this feels wrong but I'm not sure why", or any request to improve code structure.
5test-first-mentor
test-first-mentor skill for test-driven development practice. Use when a developer wants to implement a feature or fix but has not yet defined what success looks like in testable terms. Activates on "I want to build X", "I'm going to implement Y", or any intent to write implementation before the acceptance criteria and test cases are fully defined.
5