Independent second-opinion code review using Codex CLI. Use when: wanting an external AI reviewer's perspective, cross-validating before push, getting a second pair of eyes. Triggers on: '/peer-review', 'codex review', 'second opinion', 'peer review my changes'.
Use when reviewing a plan or spec for developer-facing API, CLI, SDK, MCP, plugin, integration guide, getting-started documentation, or developer onboarding design before implementation.
Use when reviewing a plan from a founder or product-ceo perspective and you need to challenge premises, choose scope expansion vs hold vs reduction, and push for the best product outcome.
Use when reviewing an execution plan and you need engineering scrutiny across architecture, data flow, diagrams, edge cases, test coverage, and performance.
Use when the user asks for a report-only browser QA pass on a web application, live site, preview URL, authenticated app flow, or release candidate without making code changes.
Use when the user explicitly requests security best practices guidance, a security review or report, or secure-by-default coding help for Python, JavaScript or TypeScript, or Go code.
Use when auditing the live design quality of a site without changing code. Trigger on "site-design-audit", design audit, visual QA, AI slop detection, typography review, spacing review, hierarchy review, or requests to review a rendered site and optionally infer DESIGN.md.
Use when auditing a live site's design and then fixing the issues in source code. Trigger on "site-design-fix", design fix loop, visual QA with fixes, AI slop cleanup, frontend polish from screenshots, or requests to audit then repair live UI issues.
Research → Plan → Code workflow. Enforces evidence-based reasoning, codebase research, and structured planning before code modifications. Applied automatically for moderate+ tasks.
Use when writing, reviewing, or optimizing Supabase or Postgres queries, schema designs, indexes, row-level security policies, or database configuration for performance and correctness.
Use when writing, reviewing, or refactoring React or Next.js code and you need performance-oriented guidance for components, data fetching, rendering, or bundle size decisions.
Delegate a complete implementation, investigation, or debugging unit to Cursor CLI, then let Codex accept and finish the result. Use when the user wants to use Cursor capacity or reduce Codex work through delegation, with resumable sessions and explicit task boundaries.
Use when the user explicitly asks for a deep local code review, PR review, bug hunt, pre-merge review, or Ultra Review style review with high confidence findings.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.