code-review
/code-review
Review a code diff for correctness, regressions, security, compatibility, and maintainability. Use when asked to review a proposed or completed change.
- Author
- helx0071 ↗
- Repository
- skillsmo ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review a code diff for correctness, regressions, security, compatibility, and maintainability. Use when asked to review a proposed or completed change.
Original author description
Review a code diff for correctness, regressions, security, compatibility, and maintainability. Use when asked to review a proposed or completed change.
How it works
- Goal
- Workflow
- Decision rules
- Boundaries
- Completion standard
- Further reading
SKILL.md preview
--- name: code-review description: "Review a code diff for correctness, regressions, security, compatibility, and maintainability. Use when asked to review a proposed or completed change." --- # Code change review ## Goal Report actionable defects with evidence while keeping review independent from implementation. ## Workflow 1. Read project instructions, change description, relevant requirements, and the complete diff. 2. Trace changed behavior through callers, data flows, error paths, and affected tests or contracts. 3. Check correctness, edge cases, authorization, data integrity, compatibility, and unintended scope. 4. Validate suspected issues against source or reproducible evidence; distinguish findings from questions and suggestions. 5. Report findings by impact with file/line evidence and a concrete remediation or verification path. ## Decision rules - Review behavior and risks before style preferences. - Prioritize issues that can cause incorrect results, data loss, security exposure, or user-visible failure. - No finding is not proof that the change is defect-free. ## Boundaries - Do not modify the diff during a read-only review unless the user asks for fixes. - Do not report speculative issues as confirmed defects. ## Completion standard Return the requested artifact or findings with enough evidence for a reviewer to understand what changed, what was checked, and what remains uncertain. Distinguish observed facts, inferred risks, and unverified assumptions. Keep the scope tied to the user's request. ## Further reading - [Field guide](references/field-guide.md) — use for task-specific review questions and edge cases. - [Source and rights notes](references/source-notes.md) — use when maintaining this package or reviewing its provenance.
Files in this package (3)
- SKILL.md 2 KB
- references/field-guide.md 1 KB
- references/source-notes.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · helx0071/skillsmo | 90 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version d9aae6f449ee (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 80Code review
Review a diff or module for correctness, security, regressions, and missing tests. Use when the user asks for a review or before shipping a change. - 100go-review
Senior Go code reviewer for comprehensive code reviews focused on correctness, security, performance, and maintainability. Use when reviewing Go code for bugs, best practices, and production readiness. - 100cx-code-review
Use for a read-only multi-pass review of your own diff, changed files, or code snippet across logic correctness, security, performance, style, and maintainability before verification or PR handoff. - 100audit-code-review
Review a PR or diff for correctness, security, and maintainability. Use for a pull request, a named change set, or "review my changes". Repo-wide anti-patterns → audit-code-quality. Bulk transforms → audit-codemod-safety. - 100pr-code-reviewer
Reviews a GitHub pull request or focused branch diff for correctness, regressions, security, compatibility, test gaps, and maintainability. Use when an implementation needs an independent source-aware review before merge. Produces prioritized findings with evidence and… - 90ce-code-review
Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.