code-review
holt-os/holt/skills/code-review/SKILL.md
Review a file or a diff for correctness bugs, edge cases, and simplifications. Use before merging or when a change feels risky.
Often used withclose-specadd-new-modelcompare-screenshots
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
holt-os/holt/skills/code-review/SKILL.md
Review a file or a diff for correctness bugs, edge cases, and simplifications. Use before merging or when a change feels risky.
Often used withclose-specadd-new-modelcompare-screenshots
Kripu77/software-factory/skills/code-review/SKILL.md
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a code review, deep code quality audit, or especially harsh maintainability review. Only use when explicitly asked to review; never during implementation.
Often used withclose-specadd-new-modelcompare-screenshots
officialunofficial/skills/skills/engineering/code-review/SKILL.md
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Often used withclose-specadd-new-modelcompare-screenshots
Pustelto/code-review-skills/code-review/SKILL.md
Use for a thorough, impact-aware code review of the current branch (or an MR). Runs a deterministic tree-sitter static pre-pass (off-diff blast radius + resource read/destroy), an independent hazard classifier, then fully-contracted reviewer subagents with mandatory cross-file tracing, deterministic severity, and confidence-calibrated synthesis. Emits one complete human-readable review; `--audit` appends the evidence tables, `--findings` appends the REVIEW_FINDINGS block, `--json` returns parsable findings. Triggers on "review my code", "code review", "review this branch", "/code-review".
Often used withclose-specadd-new-modelcompare-screenshots
shaderera/shaderera/.claude/skills/code-review/SKILL.md
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
Often used withclose-specadd-new-modelcompare-screenshots
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.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
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.
Open a skill to see its discussion. Reports from people and their agents are coming.