Code review using specialized subagents. Analyzes behavior and tests, security, reliability and performance, and maintainability. Use when reviewing a remote PR or local code, including unpushed/uncommitted changes. Pass --plan or --plan=<path> to check the diff against an implementation plan or task list.
Two-axis review of the diff since a fixed point: Standards (repo conventions) and Spec (ticket/PRD fidelity). Use when the user wants to review a branch, PR, WIP changes, or asks to \"review since X\".
Review a requested local change for evidence-backed defects, return actionable findings directly to the caller, and promote only confirmed prevention rules. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.
Review your own local code changes before pushing or creating a PR. Use when: the user wants to self-review staged or unstaged changes, check code quality before committing, or get feedback on work-in-progress. Covers readability, patterns, error handling, performance, and security. Do NOT use when: reviewing an existing pull request (use pr-review), reviewing code you didn't write, or when changes are already pushed to remote.
Review pull requests and diffs in guide — the source of the rios0rios0 engineering standards, its wiki, and the generated AI-assistant rule files — against its own standards, with extra weight on wiki page-name uniqueness, link integrity, and the generator inputs. Use when reviewing a PR, a branch, or staged changes here.
Review code for correctness, security, performance, and maintainability. Use when reviewing pull requests, examining code changes, or when the user asks for a code review.
Use when reviewing changed code before committing or after completing a feature — checks performance, architecture, type safety, and code quality against project standards
Pragmatic code review & pre-push quality gate. Use when the user says "review code", "check code quality", "any issues with this code", "ready to push", "prepare commit", "submit code", "push to remote", or any variation requesting code inspection before merging or pushing.
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.