code-review

Installation
SKILL.md

Code Review Guidelines

Use this personal review lens alongside official review guidance. Review for production failures: broken behavior, corrupted data, bypassed permissions, hidden errors, unsafe future changes, and realistic performance/resource problems. Avoid nitpicks without practical impact.

Establish Scope And Authority

Ground findings in the actual code and stated requirements, not earlier conversation history. Inspect enough surrounding implementation, callers, tests, jobs, clients and integrations to understand the changed path; individually reasonable diff lines do not establish correctness.

Trace inputs, existing/persisted states, ownership/tenant/role/session assumptions, side effects and ordering, errors, and downstream callers. Preserve original behavior in suggestions unless the task authorizes changing it. Raise business-logic defects without waiting for permission; label ambiguous intent and ask before implementing an unauthorized behavior change. Suspicious existing behavior is a question/risk, not permission to fix it silently. A read-only assignment stays read-only.

Resources Used By The Review

A solo/read-only review may still create files and processes within its permitted scope. Use project runners and compatible outputs. Before an isolated snapshot/worktree or build directory, record exact paths, owner, purpose, cleanup point and process/session identity. Preserve shared services, caches and uncommitted work; a location/name/age alone does not establish ownership.

At each completed review round, failure or cancellation, save findings/minimal reproduction evidence, stop owned processes/writers, release handles, then remove unused disposable data/build outputs. Revalidate surviving PID identities before signalling and confirm no consumer uses a path before deletion. Verify process-tree exit and path removal, not merely successful shutdown or an empty inventory. Report blocked inspection/removal with exact resource/error; never claim it clean. A finished report or deleted thread does not reclaim its cache.

During continuing work, compatible resources may transfer only when the recipient accepts ownership and can access them. Retained outputs need a named owner, reason and expiry; the current owner remains responsible until acceptance. Report closed/removed, retained, or cleanup blocked explicitly. Use testing teardown details when available and executing tests, without making the safeguards above depend on its installation.

Required Review Passes

Installs
19
Repository
noih/dev-skills
First Seen
Apr 29, 2026