Pull request review checklist for finfocus. Lists the invariants a reviewer should check that linters and tests do not catch, such as secret redaction, stdout discipline, cache-key completeness, cost-math conventions, plugin module boundaries, MCP exposure, and test isolation.
코드 변경(작업 트리 diff·브랜치·PR·경로·커밋 범위)을 **읽기 전용**으로 검토해, 실제로 확인한 발견만 보고한다. '리뷰해줘·검토해줘·이 diff 봐줘·PR 봐줘·머지해도 되나·이 수정 괜찮아?·내가 고친 거 다시 봐줘' 류 요청, 그리고 스스로 수정을 마친 뒤 되짚을 때. 버그 진단('이거 왜 안 돼')에도 같은 검사 축을 쓴다. 리뷰는 독립 매니저가 먼저 혼자 읽고, 파일이 많으면 **겹치지 않는 파일 묶음**으로만 나눈다(관점·발견 수로 나누지 않는다). 발견마다 한 동작으로 확인한 뒤에만 보고하고, 고치지 않는다 — 수정은 사용자가 따로 시킬 때 별도 단계다.
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Multi-agent deep review for code PRs in any repo. Use when asked to "deep review this PR," "multi-agent review," "review #N with subagents," "thorough review of this branch," or "is this PR ready to merge." Orchestrates Copilot + parallel subagents (adversarial, operational, reference-comparison) with scope-based escalation, stale-finding triage, and a hard iteration cap.
AI-driven code review workflow that reviews uncommitted changes using a discoverable reviewer profile, presents findings for human decision, and iterates until approved. Supports --unattended for automated iteration. Use when reviewing code before commit or PR. Activated by commands: /start, /continue, /clean.
Performs a thorough code review of the current changes or a specified file / pull request. Covers correctness, security, performance, readability, and adherence to project conventions. Outputs prioritised, actionable feedback. TRIGGER when the user writes /code-review or asks for a code review, PR review, or feedback on their code.
Review Luau code for style compliance, type safety, server authority, error handling, and performance. Use for reviewing a file, a PR-sized change, or a whole module.
Systematic code review with structured output and actionable findings. Use when reviewing code, auditing quality, checking for bugs, security vulnerabilities, or performance issues.
Use before commit, deploy, or PR merge, or when operator asks "review this diff" / "is this safe?"; reviews diff vs spec, decisions, maintainability, scope, tests, rollback. Do NOT write or fix code — review only.
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".
name: code-review
description: Default target is the current branch diff vs main.
--
# code-review - E2E healer team review
The team's own review procedure. It layers **things
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.