code-review
/code-review
Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it.
- Author
- dakotacolorado ↗
- Repository
- honed ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- 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
Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it.
Original author description
Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it.
How it works
- Read for intent first
- In order of importance
- Saying it
- Before you approve
SKILL.md preview
--- name: code-review description: Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it. --- # Reviewing code ## Read for intent first Read the PR description and any linked ticket before the diff. Review the change against what it claims to do; if it doesn't say, ask before guessing. ## In order of importance 1. **Correctness.** Wrong results, unhandled errors, edge cases (empty, null, very large, concurrent), off-by-one, resource leaks. 2. **Risk.** Security (input reaching queries, shells or HTML unescaped; secrets; authorization), data loss, migrations, anything hard to undo. 3. **Tests.** Does a test fail without this change? Are the risky paths covered? 4. **Design.** Does it fit how the codebase already does this? Is anything duplicated that exists already? 5. **Readability.** Names, size, clarity. Last, and only where it matters. ## Saying it - Lead each comment with its weight: **blocking**, **should fix**, or **nit**. - Point to the line, say what goes wrong and when, and suggest a fix when you have one. - Ask instead of assert when you might be missing context. - Don't comment on what a formatter or linter would catch. ## Before you approve Run it or its tests if you can. Say plainly what you checked and what you didn't.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · dakotacolorado/honed | 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 17e8ab907754 (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
- 90code-review-and-quality
Reviews a diff for correctness, risk, and missing evidence before merge. Use when preparing a change for commit, reviewing a pull request, reviewing AI-generated code, or deciding whether work is genuinely done. - 100review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill". - 90review
Review a pull request or diff for this repository against otari's project standards. Use when asked to review a PR, inspect a diff, or prepare review feedback. - 90dev-pr-review
Use for reviewing a branch, pull request, local diff, or implementation plan before merge, including alignment of existing PR metadata with the diff and delivery state. - 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. - 90reviews
Review a pull request or code change for code health. Use when a user asks to "code review", "review this PR", or "review this change".