ffsshhttiikkSkillcode-review
ffsshhttiikk/opencode-agents-skills/code-review/SKILL.md
Code review best practices and guidelines
Find the best CLAUDE.md, AGENTS.md and Claude skills
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Best matches · from page 15Worked for most · soon
ffsshhttiikkSkill
FooJiaYinSkillcode-review
FooJiaYin/dev-skills/skills/code-review/SKILL.md
Multi-agent review of the local git diff. Spawns parallel agents covering bugs+security, CLAUDE.md adherence, git history, performance, plan adherence, and quality+architecture; tiers findings by confidence (Critical/Warning/Suggestion/Nit) and drops only auto-zeroed false positives; writes REVIEW.md. Also has a whole-tree mode (`/code-review tree [glob]`, or wording like 「審核架構／有沒有重複」) that audits the current source for duplication and missing abstractions instead of a diff. Use when the user says "review my changes", "review this branch", "code review", "審核架構", or invokes /code-review. Supersedes the built-in /code-review in repos using dev-skills — invoke only this one.
gspencergoogSkillcode-review
gspencergoog/skills/skills/code-review/SKILL.md
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback. Use when you need to review code changes thoroughly.
hehee9Skillcode-review
hehee9/skill-stash/skills/code-review/SKILL.md
Perform a mandatory scoped code review for the code changed in the current task. Use when Codex has implemented or modified code and must review the touched scope for requirement compliance, existing style consistency, stability, scalability, efficiency, security, integration with real code paths, compatibility, dry-run behavior, structural clarity, helper boundaries, fallback justification, and silent error masking; a user request to use this skill counts as explicit permission to use 1-3 read-only review subagents for broad changed scopes; fix any discovered issue immediately unless it requires a user decision or integration with code that does not exist yet.
iasiv5Skillcode-review
iasiv5/skills/code-review/SKILL.md
代码审查助手。用户请求 review 代码、PR 或 commit，或寻找 bug 时使用。以 Spec（需求/规格符合性）与 Standards（项目规范符合性）双轨审查，覆盖 C/C++、嵌入式、BIOS/UEFI、BMC 专项。
igorkulmanSkillcode-review
igorkulman/pi-skills/skills/code-review/SKILL.md
Review code changes either from the local working tree/current branch or from a GitLab merge request. Use when the user asks for a code review, MR review, branch review, review of local/staged changes, or wants findings that can optionally be posted back to GitLab via glab.
jacksonwilliamsvaSkillcode-review
jacksonwilliamsva/kiro-skills-library/skills/code-review/SKILL.md
Automated code review for pull requests using parallel analysis with confidence-based scoring to filter false positives. Use when the user asks to review a PR, review code changes, or run a code review.
joelaharris98Skillcode-review
joelaharris98/legal-ai-engineering-lab/.agents/skills/code-review/SKILL.md
Automatically use before committing a substantial change; when work on an experiment is finished and the question is whether it answered the hypothesis it stated and whether it is well built; when the owner asks whether something is any good, is ready, or can be relied on; when they ask whether a piece of work is done and they can move on to the next thing; and when they ask for a review of changes, a diff, a branch, or a pull request. Reviews on two separate axes - whether it did what was asked, and whether it is well built - and reports them apart, because reporting them together lets a pass on one hide a failure on the other. Do not use for a routine question about a single line, for a change small enough that the answer is the answer, on code still being written, or immediately after a review with no work in between.
joelaharris98Skillcode-review
joelaharris98/legal-ai-engineering-lab/.claude/skills/code-review/SKILL.md
Automatically use before committing a substantial change; when work on an experiment is finished and the question is whether it answered the hypothesis it stated and whether it is well built; when the owner asks whether something is any good, is ready, or can be relied on; when they ask whether a piece of work is done and they can move on to the next thing; and when they ask for a review of changes, a diff, a branch, or a pull request. Reviews on two separate axes - whether it did what was asked, and whether it is well built - and reports them apart, because reporting them together lets a pass on one hide a failure on the other. Do not use for a routine question about a single line, for a change small enough that the answer is the answer, on code still being written, or immediately after a review with no work in between.
johanolofsson72Skillcode-review
johanolofsson72/Claude/.claude/skills/code-review/SKILL.md
Reviews code changes for bugs, security issues, performance problems, and adherence to project conventions. Use when the user asks for code review, PR review, or after significant code changes. Trigger words include review, check code, PR.
juanitourquizaSkillcode-review
juanitourquiza/shipframe/skills/code-review/SKILL.md
Review changed code before commit or PR with fast checks plus SOLID, security, performance, and test coverage audit.
kings0527Skillcode-review
kings0527/pi-harness/skills/mattpocock/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".
LOUSANPANGSkillcode-review
LOUSANPANG/agent-skills/skills/engineering/code-review/SKILL.md
六维代码评审：按 correctness / architecture / security / performance / UX / maintainability 逐维检查改动并输出分级 findings。当用户要求 review、审计代码或合并前检查时使用；覆盖评审范围确认、六维判定与 blocker / warning / nit 分级输出。
ly0o0oSkillcode-review
ly0o0o/codex-engineering-skills/skills/code-review/SKILL.md
从需求意图、架构、资源消耗、代码组织、可维护性与优雅性角度执行严格代码评审。
miketrombaSkillcode-review
miketromba/skills/skills/code-review/SKILL.md
Review a proposed code change using Codex's standard review rubric. Use when asked to review a diff, PR, branch, local change set, staged changes, or any code modification for actionable correctness, security, performance, maintainability, or regression findings.
mpaaratingSkillcode-review
mpaarating/ai-workflow-kit/skills/code-review/SKILL.md
Multi-persona code review with Architect and Nitpicker perspectives
nafeeurSkillcode-review
nafeeur/MaskShift/skills/code-review/SKILL.md
Review changes for real correctness, maintainability, regressions, missing tests, and integration defects with low-noise findings.
onmyway133Skillcode_review
onmyway133/skills/skills/code-review/SKILL.md
Comprehensive code review for quality, security, performance, and best practices across any language
OpenCovenSkillcode-review
OpenCoven/psyche-build/.github/skills/code-review/SKILL.md
Review code changes in the Psyche Build repository for high-confidence, actionable defects. Use this skill whenever the user asks to review a working tree, staged changes, a commit, commit range, branch, pull request, patch, regression, or implementation for correctness and risk—even if they do not explicitly say "code review." It is read-only and repository-specific across TypeScript/Node, React/Vue/Ink, Tauri Rust and web bundles, Swift/iOS, protocols, generated files, packaging, CI, and release surfaces. Do not use it for an explicit vulnerability or exploit hunt; use the dedicated security-review workflow for that request.
pvalenaSkillCode Review
pvalena/claude-skills/review/SKILL.md
Complete workflow for reviewing patches/commits, documenting findings, and formatting results
Agent instruction files
What are agent instruction files?
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.