Loading...
Loading...
Found 17 Skills
Remove AI-generated code slop from the current branch. Use when the user says "deslop" or asks to clean up AI slop, remove AI code patterns, or clean the branch before committing.
Audits codebases for common security vulnerabilities that AI coding assistants introduce in "vibe-coded" applications. Checks for exposed API keys, broken access control (Supabase RLS, Firebase rules), missing auth validation, client-side trust issues, insecure payment flows, and more. Use this skill whenever the user asks about security, wants a code review, mentions "vibe coding", or when you're writing or reviewing code that handles authentication, payments, database access, API keys, secrets, or user data — even if they don't explicitly mention security. Also trigger when the user says things like "is this safe?", "check my code", "audit this", "review for vulnerabilities", or "can someone hack this?".
Code Review. When users request reviews of code changes, pre-merge checks, or want to identify hidden issues in AI-generated code, conduct reviews from four dimensions: correctness, security, performance, and maintainability, and output structured opinions with severity levels. Use to review code changes, diffs, or AI-generated code before merging.
Remove AI-generated slop introduced on this branch relative to main.
Remove AI slop from a branch and make its code easier to read. Use when asked to tidy or deslop code.