code-review
/code-review
This skill should be used when reviewing a branch, pull request, working tree, or changes since a commit for repository standards and the user's requested behavior.
- Author
- oyadotai ↗
- Repository
- oya-browser ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.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
This skill should be used when reviewing a branch, pull request, working tree, or changes since a commit for repository standards and the user's requested behavior.
Original author description
This skill should be used when reviewing a branch, pull request, working tree, or changes since a commit for repository standards and the user's requested behavior.
How it works
- Establish scope
- Standards pass
- Spec pass
- Report
SKILL.md preview
--- name: code-review description: "This skill should be used when reviewing a branch, pull request, working tree, or changes since a commit for repository standards and the user's requested behavior." --- # Review standards and requested behavior Review two distinct questions: whether the change follows the project's documented standards, and whether it implements the requested behavior. Perform both passes within the assigned role. Delegate only when explicitly authorized and the assigned tools support delegation. Return the report to the coordinator; remote comments or issue publication require existing authorization. ## Establish scope Read the assignment and identify the requested files or comparison. For branch work, resolve the supplied ref and inspect the appropriate merge-base diff and commit list. For an exact commit comparison, use the requested endpoints. For work in progress, inspect unstaged and staged changes and relevant untracked files; a committed-only diff misses that assignment. Name the range reviewed, and report invalid refs or empty scope plainly. Read applicable repository instructions, surrounding code, callers, and tests. Include CONTRIBUTING.md and CODING_STANDARDS.md when present. Recover acceptance criteria from the user's request, supplied spec, or relevant local issue material. Read linked remote sources through Oya Browser when access is authorized. Use the current request as the spec when no formal document exists. State missing requirements as coverage limits rather than inventing them or requiring tracker setup. ## Standards pass Apply documented rules in their proper scope and account for established exceptions. Trace correctness, ownership, compatibility, failure handling, and concurrency through real callers. Skip mechanical nits already enforced by tooling. Use [references/design-signals.md](references/design-signals.md) only to guide investigation of maintainability; a code smell alone does not establish a defect. Support each blocking finding with a reachable case or a concrete documented requirement, source location, impact, and a small repair. Keep optional maintainability advice separate and include it only when requested. Respect a correctness-only review's scope. ## Spec pass Map each requirement to implementation and evidence. Look for missing or partial behavior, incorrect interpretation, scope growth, and apparent success that fails on cancellation, retry, disconnect, restart, or duplicate input. Inspect affected callers beyond the edited hunk. Distinguish a demonstrated defect from an unresolved question and from a preexisting issue. ## Report Lead with the verdict and covered scope. Use separate **Standards** and **Spec** sections, each with its result, supported findings, and coverage limits. For each finding give severity, file/line, triggering input or state, expected and actual behavior, evidence, and smallest repair. Cross-reference a shared underlying defect instead of counting it twice. An empty findings list is valid; do not manufacture findings to fill a section. List exact checks executed and their results. A passing check supports only the behavior it exercises. Write or run tests only within the user's authorization. Preserve implementation unless a repair was assigned. Use the team's findings asset when acting as reviewer; fit these two passes into it without duplicating the report. Adapted from Matt Pocock's engineering skills; see [SOURCE.md](SOURCE.md) and [LICENSE](LICENSE).
Files in this package (4)
- LICENSE 1 KB
- SKILL.md 3 KB
- SOURCE.md 1 KB
- references/design-signals.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · oyadotai/oya-browser | 85 | 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 |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 9b23da707759 (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
- 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". - 100dev-review
Use when a diff, branch or PR needs review before merge, on correctness, standards and the spec. - 100create-pull-request
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository. - 100review
Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a… - 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. - 90review-a-pull-request
A careful code review of a change, a branch or a pull request: correctness, tests, security, readability, with findings ordered by how much they matter. Use when the owner asks you to review code, a diff, a branch or a PR.